37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1752220 |
Time | |
Date | 202007 |
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 | Skylark 175 |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Route In Use | Visual Approach |
Flight Plan | None |
Person 1 | |
Function | Instructor Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 226 Flight Crew Total 551 Flight Crew Type 194 |
Events | |
Anomaly | Ground Event / Encounter Loss Of Aircraft Control Ground Event / Encounter Ground Strike - Aircraft Ground Excursion Runway |
Narrative:
Upon landing; my student and I had a propeller strike on the runway surface. With winds at 360 gusting up to 17 kts; we had a healthy crosswind. My student was handling the wind conditions well and made proper control inputs throughout the landing. Upon landing; the aircraft entered an extremely nose-low attitude which caused the propeller to strike the runway surface. As the plane began to enter its nose-low attitude; I realized that my student was not handling the after-landing process as I had anticipated. I immediately reached for the controls to make prompt corrective inputs and recover the aircraft into a normal after-landing attitude.focusing on recovering the nose-low attitude and trying to bring the aircraft back into a safe position was all that occupied my mind at the moment. I failed to say 'my controls' to my student which I believe; in turn; caused the student to remain on the controls and brakes while I attempted to recover the aircraft. With both of us on the controls; the aircraft was not responding properly to either of our inputs. The aircraft continued to travel to the right of centerline and exited the paved surface of the runway approximately 10-15 ft. Where we brought it to a stop.as the CFI (flight instructor); my largest takeaway is in the area of communication with my student. Because of my immediate reaction to the situation; I did not communicate to him my intent to take control of the aircraft. I did not tell him to get his hands and feet off the controls. I did not make sure that he knew without doubt that I needed him off of his controls so I could have effective use of mine.my action moving forward with students will be specifically focused on effective communication and making sure there are no barriers between the message I send them; then confirming that they received that same message. Emphasizing the fact that if I say 'my controls' at any point during flight or ground operations; I need them to be 100% off of all the flight controls so I can have immediate and full effective use of my flight controls.during all phases of flight I will be taking specific action to verify and assure safety of flight so my student is briefed on what is to come as well as for my knowledge that the student understands what I am communicating to them. Another practice I will be revisiting with my students will be demonstrating safety risk management as a normal part of the landing and after-landing phases of flight.
Original NASA ASRS Text
Title: C175 Flight Instructor reported a runway excursion occurred when he failed to properly communicate to his student his intention to take control of the aircraft.
Narrative: Upon landing; my student and I had a propeller strike on the runway surface. With winds at 360 gusting up to 17 kts; we had a healthy crosswind. My student was handling the wind conditions well and made proper control inputs throughout the landing. Upon landing; the aircraft entered an extremely nose-low attitude which caused the propeller to strike the runway surface. As the plane began to enter its nose-low attitude; I realized that my student was not handling the after-landing process as I had anticipated. I immediately reached for the controls to make prompt corrective inputs and recover the aircraft into a normal after-landing attitude.Focusing on recovering the nose-low attitude and trying to bring the aircraft back into a safe position was all that occupied my mind at the moment. I failed to say 'My Controls' to my student which I believe; in turn; caused the student to remain on the controls and brakes while I attempted to recover the aircraft. With both of us on the controls; the aircraft was not responding properly to either of our inputs. The aircraft continued to travel to the right of centerline and exited the paved surface of the runway approximately 10-15 ft. where we brought it to a stop.As the CFI (Flight Instructor); my largest takeaway is in the area of communication with my student. Because of my immediate reaction to the situation; I did not communicate to him my intent to take control of the aircraft. I did not tell him to get his hands and feet off the controls. I did not make sure that he knew without doubt that I needed him off of his controls so I could have effective use of mine.My action moving forward with students will be specifically focused on effective communication and making sure there are no barriers between the message I send them; then confirming that they received that same message. Emphasizing the fact that if I say 'my controls' at any point during flight or ground operations; I need them to be 100% off of all the flight controls so I can have immediate and full effective use of my flight controls.During all phases of flight I will be taking specific action to verify and assure safety of flight so my student is briefed on what is to come as well as for my knowledge that the student understands what I am communicating to them. Another practice I will be revisiting with my students will be demonstrating safety risk management as a normal part of the landing and after-landing phases of flight.
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.