37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 179365 |
Time | |
Date | 199105 |
Day | Sun |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : bed |
State Reference | MA |
Altitude | agl bound lower : 0 agl bound upper : 0 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | general aviation : personal |
Make Model Name | Small Aircraft, Low Wing, 1 Eng, Retractable Gear |
Flight Phase | landing other |
Flight Plan | VFR |
Person 1 | |
Affiliation | Other |
Function | flight crew : single pilot |
Qualification | pilot : private pilot : instrument |
Experience | flight time last 90 days : 15 flight time total : 670 flight time type : 210 |
ASRS Report | 179365 |
Events | |
Anomaly | non adherence : published procedure non adherence : far other spatial deviation |
Independent Detector | other flight crewa |
Resolutory Action | none taken : detected after the fact |
Consequence | other |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Gear up landing. Didn't properly deploy gear for landing confign. Circumstances: clear day, controled airport, busy afternoon, was advised #3 to land, 2 other aircraft in traffic pattern. Then was cleared #2 to land. Never saw other aircraft in pattern (i.e., second one). I believe this preoccupation to find the other traffic definitely led to this incident. The other gumps were normal. Landed with full flaps and propeller in proper position, etc. It was a very sobering experience, but I have since realized that it would be helpful (and I'm not passing the responsibility to anyone) if the tower would call gear down and locked on final as they do in the military and I believe canada, also. Safety is the name of the game, and this surely would help. It is also the unofficial opinion of the airport management and the FAA (located on the field) that this facility has an exceptionally high # of these incidents. Finally, I realize that the PIC is the one responsible, but there seems to be more and more confusion at this field, possibly due to the fact that it is an extremely busy airport, but one that has many controllers being trained here. Hope this helps your data bank and helps prevent another incident such as mine.
Original NASA ASRS Text
Title: GA SMA GEAR UP LNDG AT BED.
Narrative: GEAR UP LNDG. DIDN'T PROPERLY DEPLOY GEAR FOR LNDG CONFIGN. CIRCUMSTANCES: CLR DAY, CTLED ARPT, BUSY AFTERNOON, WAS ADVISED #3 TO LAND, 2 OTHER ACFT IN TFC PATTERN. THEN WAS CLRED #2 TO LAND. NEVER SAW OTHER ACFT IN PATTERN (I.E., SECOND ONE). I BELIEVE THIS PREOCCUPATION TO FIND THE OTHER TFC DEFINITELY LED TO THIS INCIDENT. THE OTHER GUMPS WERE NORMAL. LANDED WITH FULL FLAPS AND PROP IN PROPER POS, ETC. IT WAS A VERY SOBERING EXPERIENCE, BUT I HAVE SINCE REALIZED THAT IT WOULD BE HELPFUL (AND I'M NOT PASSING THE RESPONSIBILITY TO ANYONE) IF THE TWR WOULD CALL GEAR DOWN AND LOCKED ON FINAL AS THEY DO IN THE MIL AND I BELIEVE CANADA, ALSO. SAFETY IS THE NAME OF THE GAME, AND THIS SURELY WOULD HELP. IT IS ALSO THE UNOFFICIAL OPINION OF THE ARPT MGMNT AND THE FAA (LOCATED ON THE FIELD) THAT THIS FAC HAS AN EXCEPTIONALLY HIGH # OF THESE INCIDENTS. FINALLY, I REALIZE THAT THE PIC IS THE ONE RESPONSIBLE, BUT THERE SEEMS TO BE MORE AND MORE CONFUSION AT THIS FIELD, POSSIBLY DUE TO THE FACT THAT IT IS AN EXTREMELY BUSY ARPT, BUT ONE THAT HAS MANY CTLRS BEING TRAINED HERE. HOPE THIS HELPS YOUR DATA BANK AND HELPS PREVENT ANOTHER INCIDENT SUCH AS MINE.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.