37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1300262 |
Time | |
Date | 201510 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | ZZZ.TRACON |
State Reference | US |
Environment | |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Skyhawk 172/Cutlass 172 |
Operating Under FAR Part | Part 91 |
Person 1 | |
Function | Pilot Flying Instructor |
Events | |
Anomaly | Flight Deck / Cabin / Aircraft Event Smoke / Fire / Fumes / Odor |
Narrative:
On a routine training flight over the coast; about 7;500 feet the crew of two pilot instructing (pi) and pilot under instruction (pui) were giving instruction on and practicing demonstration stalls. The air was cool and improved aircraft was noted during the climb and all systems normal. The crew had climbed to 8;000 and had been roughly level for about 10-15 minutes at reduced power settings while conducting accelerated and cross-controlled stalls. During the recovery of a cross-controlled stall a strong electrical/ burning smell was noted by pi and confirmed by pui. Light smoke/fumes were noted in the cockpit and pi stated this was emergency and to get the checklist. Pi took flight controls and executed turning off of master electrical switch; avionics; pitot-heat and lights. A steep spiral was initiated to about 3;000 feet followed by an emergency descent maneuver towards the nearby airport. Traffic was observed to be to the left for runway 18. The position was ideal for entry. The fumes were still present and the odor strong and the crew looked for sources of fire. None were found and the pi elected to perform an emergency landing on runway 18 and the crew was briefed for emergency evacuation to follow. Pi maneuvered direct to the runway and entered a close (1/2) mile downwind leg and began a descent abeam. Final traffic was identified sel low wing aircraft and followed to runway. Final approach speed was about 70 KIAS as recommended for the configuration; the electric flaps were not available because the burning odor was still strong. The traffic seemed to land then accelerate to takeoff; then slow again. The PF slowed to prepare for a landing but the aircraft was still on the runway. Pi was hoping to not go-around. The traffic turned onto the taxiway and cleared the runway. The pi landing and immediately cleared the runway and shut down the engine and evacuated the airplane with fuel shutoff. The [company] supervisor was contacted by phone.in the event of an emergency landing; be prepared to avoid traffic. Have a contingency landing prepared such as abeam taxiway clear of traffic or the best clear grass available. It would be important to weigh the fact that an emergency landing may cause more damage than whatever was prompting the emergency approach.
Original NASA ASRS Text
Title: C172 instructor pilot reported executing an emergency landing when a strong electrical burning smell was noticed.
Narrative: On a routine training flight over the coast; about 7;500 feet the crew of two Pilot Instructing (PI) and Pilot Under Instruction (PUI) were giving instruction on and practicing demonstration stalls. The air was cool and improved aircraft was noted during the climb and all systems normal. The crew had climbed to 8;000 and had been roughly level for about 10-15 minutes at reduced power settings while conducting accelerated and cross-controlled stalls. During the recovery of a cross-controlled stall a strong electrical/ burning smell was noted by PI and confirmed by PUI. Light smoke/fumes were noted in the cockpit and PI stated this was emergency and to get the checklist. PI took flight controls and executed turning off of master electrical switch; avionics; pitot-heat and lights. A steep spiral was initiated to about 3;000 feet followed by an emergency descent maneuver towards the nearby airport. Traffic was observed to be to the left for Runway 18. The position was ideal for entry. The fumes were still present and the odor strong and the crew looked for sources of fire. None were found and the PI elected to perform an emergency landing on Runway 18 and the crew was briefed for emergency evacuation to follow. PI maneuvered direct to the runway and entered a close (1/2) mile downwind leg and began a descent abeam. Final traffic was identified SEL low wing aircraft and followed to runway. Final approach speed was about 70 KIAS as recommended for the configuration; the electric flaps were not available because the burning odor was still strong. The traffic seemed to land then accelerate to takeoff; then slow again. The PF slowed to prepare for a landing but the aircraft was still on the runway. PI was hoping to not go-around. The traffic turned onto the taxiway and cleared the runway. The PI landing and immediately cleared the runway and shut down the engine and evacuated the airplane with fuel shutoff. The [company] supervisor was contacted by phone.In the event of an emergency landing; be prepared to avoid traffic. Have a contingency landing prepared such as abeam taxiway clear of traffic or the best clear grass available. It would be important to weigh the fact that an emergency landing may cause more damage than whatever was prompting the emergency approach.
Data retrieved from NASA's ASRS site 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.