37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 200272 |
Time | |
Date | 199201 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | airport : mo49 |
State Reference | MD |
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 | descent : approach landing other other |
Flight Plan | None |
Person 1 | |
Affiliation | Other |
Function | instruction : instructor |
Qualification | pilot : instrument pilot : commercial pilot : cfi |
Experience | flight time last 90 days : 178 flight time total : 760 flight time type : 46 |
ASRS Report | 200272 |
Person 2 | |
Affiliation | Other |
Function | flight crew : single pilot instruction : trainee |
Events | |
Anomaly | conflict : ground critical non adherence : published procedure 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:
The incident happened while performing touch and go's on runway 34 at MO49. Seven touch and go's were performed before the incident occurred. Myself and the student were performing an emergency approach to landing. The power was pulled back, abeam the numbers on downwind before the gear was dropped. The horn was sounding and the student established best glide. As we rolled base another aircraft called unicom and asked for a field advisory. Unicom reported back winds, runway in use, and no reported traffic. The aircraft then announced that he would make a straight-in approach for 34. I immediately called the other aircraft and advised him that we were in the pattern doing touch and go's (please note that downwind, base, and final were called by me for all previous lndgs). The aircraft called back and asked our position. I responded telling him that we were turning short final, while looking over my shoulder for the traffic. When I turned around it was too late to take evasive action. The cause of the incident was clearly a case of distraction from the task at hand. Hearing the gear horn for an extended period of time, coupled with the muffling effect of the headsets and the communication and searching for the other aircraft created the distraction.
Original NASA ASRS Text
Title: GEAR UP LNDG.
Narrative: THE INCIDENT HAPPENED WHILE PERFORMING TOUCH AND GO'S ON RWY 34 AT MO49. SEVEN TOUCH AND GO'S WERE PERFORMED BEFORE THE INCIDENT OCCURRED. MYSELF AND THE STUDENT WERE PERFORMING AN EMER APCH TO LNDG. THE PWR WAS PULLED BACK, ABEAM THE NUMBERS ON DOWNWIND BEFORE THE GEAR WAS DROPPED. THE HORN WAS SOUNDING AND THE STUDENT ESTABLISHED BEST GLIDE. AS WE ROLLED BASE ANOTHER ACFT CALLED UNICOM AND ASKED FOR A FIELD ADVISORY. UNICOM RPTED BACK WINDS, RWY IN USE, AND NO RPTED TFC. THE ACFT THEN ANNOUNCED THAT HE WOULD MAKE A STRAIGHT-IN APCH FOR 34. I IMMEDIATELY CALLED THE OTHER ACFT AND ADVISED HIM THAT WE WERE IN THE PATTERN DOING TOUCH AND GO'S (PLEASE NOTE THAT DOWNWIND, BASE, AND FINAL WERE CALLED BY ME FOR ALL PREVIOUS LNDGS). THE ACFT CALLED BACK AND ASKED OUR POS. I RESPONDED TELLING HIM THAT WE WERE TURNING SHORT FINAL, WHILE LOOKING OVER MY SHOULDER FOR THE TFC. WHEN I TURNED AROUND IT WAS TOO LATE TO TAKE EVASIVE ACTION. THE CAUSE OF THE INCIDENT WAS CLRLY A CASE OF DISTR FROM THE TASK AT HAND. HEARING THE GEAR HORN FOR AN EXTENDED PERIOD OF TIME, COUPLED WITH THE MUFFLING EFFECT OF THE HEADSETS AND THE COM AND SEARCHING FOR THE OTHER ACFT CREATED THE DISTR.
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.