37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 953759 |
Time | |
Date | 201106 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | ZZZ.Airport |
State Reference | US |
Aircraft 1 | |
Make Model Name | M-20 Series Undifferentiated or Other Model |
Flight Phase | Initial Climb |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | SR22 |
Flight Phase | Initial Climb |
Route In Use | Vectors |
Flight Plan | IFR |
Person 1 | |
Function | Local |
Qualification | Air Traffic Control Fully Certified |
Person 2 | |
Function | Single Pilot |
Qualification | Flight Crew Instrument Flight Crew Private |
Experience | Flight Crew Last 90 Days 38 Flight Crew Total 2231 Flight Crew Type 2027 |
Events | |
Anomaly | Deviation - Altitude Excursion From Assigned Altitude Deviation - Track / Heading All Types |
Narrative:
M20P departed runway 35 with an on course heading of 335. A SR22 departed runway 17 on heading 020. After being switched to departure; the M20P started to turn back into the departure corridor and the TRACON controller stated that he was turning back northwest bound. At that point I turned the SR22 to a 090 heading to ensure separation. The M20P continued to fly erratically and I turned the SR22 to a 120 heading to further ensure separation then switched him to departure. At that time the low altitude alert began to alarm and I started to visually search for the aircraft. I observed him descending out of the clouds in a steep right turn. At that time using the override line I heard the pilot state that he having problems; needed help and wanted to get down. He was then switched to tower. When asked to say intentions the pilot stated that he needed to get down; I then cleared him to land on any runway. I then proceeded to clear multiple vehicles off of runway safety areas. I then saw the M20P on final and cleared him to land. He then landed and rolled out with no incident. This emergency situation was due to pilot disorientation.
Original NASA ASRS Text
Title: Tower Controller and M-20J pilot described an emergency return to the airport resulting from an apparent disorientation issue with the pilot of an IFR general aviation aircraft.
Narrative: M20P departed Runway 35 with an on course heading of 335. A SR22 departed Runway 17 on heading 020. After being switched to departure; the M20P started to turn back into the departure corridor and the TRACON Controller stated that he was turning back northwest bound. At that point I turned the SR22 to a 090 heading to ensure separation. The M20P continued to fly erratically and I turned the SR22 to a 120 heading to further ensure separation then switched him to Departure. At that time the low altitude alert began to alarm and I started to visually search for the aircraft. I observed him descending out of the clouds in a steep right turn. At that time using the override line I heard the pilot state that he having problems; needed help and wanted to get down. He was then switched to Tower. When asked to say intentions the pilot stated that he needed to get down; I then cleared him to land on any runway. I then proceeded to clear multiple vehicles off of Runway safety areas. I then saw the M20P on final and cleared him to land. He then landed and rolled out with no incident. This emergency situation was due to pilot disorientation.
Data retrieved from NASA's ASRS site as of April 2012 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.