 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
C172 instructor with student reports engine quitting when student applied power during a touch and go landing. The aircraft is taxied clear of the active runway and restarted. After much discussion and several runups the reporter departs for another airport and returns some time later with no problems. The aircraft is grounded upon return for maintenance inspection.
| Attributes | |
| ACN | 958146 |
| Time | |
| Date | 201107 |
| Local Time Of Day | 1201-1800 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Skyhawk 172/Cutlass 172 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Flight Plan | IFR |
| Component | |
| Aircraft Component | Engine |
| Person 1 | |
| Function | Instructor |
| Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
| Experience | Flight Crew Last 90 Days 15 Flight Crew Total 2345 Flight Crew Type 800 |
| Events | |
| Anomaly | Aircraft Equipment Problem Critical Deviation - Procedural Published Material / Policy |
Narrative:
On IFR approach requested and was approved for touch and go. Approach and landing were normal. After nosewheel touched down student applied full throttle; engine sputtered and died. I took over control and was able to taxi aircraft off active runway onto intersecting (inactive) runway. [I] notified tower of situation. Tower asked if I needed any assistance and I replied negative. Was able to restart engine and did a run-up per checklist. Everything was normal. [I] requested tower permission to taxi back to runway for takeoff. Tower had me taxi over to 'ops' area to meet with airport operations person. Taxied over to designated area and shut down. Operations person looked over aircraft and everything looked normal. Asked what happened and we agreed that engine probably flooded due to throttle being applied to briskly by student. Operations person took our names and phone numbers and had me talk with operations manager on his cell phone. Explained situation to him and he mentioned that there were mechanics on duty if I wanted/needed them. Told him that I had done a run-up and all appeared normal and would do another prior to departure. If anything looked suspicious I would have a mechanic check it prior to departure. Gave the phone back to the operations person and was cleared to restart. Restarted without problem; taxied away form operations people and did another run-up per checklist. All systems [were] normal. Contacted ground and was given permission to taxi to runway 23. On taxiway just before hold line to runway 23 performed another full run-up check per checklist. Systems were normal and I contacted the tower. [I] was cleared for takeoff. Takeoff and entire flight to and landing at hfd were normal. Upon returning to FBO; secured the plane and explained situation to owner and grounded the plane. Mechanic was checking plane when I left the airport.
Original NASA ASRS Text
Title: C172 Instructor with student reports engine quitting when student applied power during a touch and go landing. The aircraft is taxied clear of the active runway and restarted. After much discussion and several runups the reporter departs for another airport and returns some time later with no problems. The aircraft is grounded upon return for maintenance inspection.
Narrative: On IFR approach requested and was approved for touch and go. Approach and landing were normal. After nosewheel touched down student applied full throttle; engine sputtered and died. I took over control and was able to taxi aircraft off active runway onto intersecting (inactive) runway. [I] notified Tower of situation. Tower asked if I needed any assistance and I replied negative. Was able to restart engine and did a run-up per checklist. Everything was normal. [I] requested tower permission to taxi back to runway for takeoff. Tower had me taxi over to 'Ops' area to meet with Airport Operations person. Taxied over to designated area and shut down. Operations person looked over aircraft and everything looked normal. Asked what happened and we agreed that engine probably flooded due to throttle being applied to briskly by student. Operations person took our names and phone numbers and had me talk with Operations Manager on his cell phone. Explained situation to him and he mentioned that there were mechanics on duty if I wanted/needed them. Told him that I had done a run-up and all appeared normal and would do another prior to departure. If anything looked suspicious I would have a mechanic check it prior to departure. Gave the phone back to the Operations person and was cleared to restart. Restarted without problem; taxied away form Operations people and did another run-up per checklist. All systems [were] normal. Contacted Ground and was given permission to taxi to Runway 23. On taxiway just before hold line to Runway 23 performed another full run-up check per checklist. Systems were normal and I contacted the Tower. [I] was cleared for takeoff. Takeoff and entire flight to and landing at HFD were normal. Upon returning to FBO; secured the plane and explained situation to owner and grounded the plane. Mechanic was checking plane when I left the airport.
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.