37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1315000 |
Time | |
Date | 201512 |
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 | SR20 |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Takeoff |
Flight Plan | None |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Multiengine Flight Crew Instrument Flight Crew Flight Instructor |
Experience | Flight Crew Last 90 Days 100 Flight Crew Total 2700 Flight Crew Type 1300 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Miss Distance | Horizontal 50 Vertical 200 |
Narrative:
I was with a student taxiing to the active runway from the ramp. Another instructor was out on the airfield with his student; preparing to send him on his first solo. The AWOS indicated winds favoring runway xx; so we made a radio call saying that we were taxiing to runway xx. At that point; I communicated by radio with the other instructor about his student's upcoming first solo; a non-critical call that could have waited until the airplane was stationary (mistake number one). As we approached the hold short line for runway yy; we slowed (but did not stop - mistake number two) and made a cursory scan for other aircraft left and right. We expected that the other instructor would be using runway xx and so we failed to catch that he was actually beginning his takeoff roll on runway yy (mistake number four). Whether his student actually called out runway yy or xx is irrelevant; my student and I heard runway xx and that's where our eyes were. We crossed the hold short line and were approaching the runway edge markings when we got an unreadable radio call; but which definitely contained the numbers runway yy. We immediately stopped and looked to our right. Sure enough; the other aircraft was on the takeoff roll about to pass in front of us. They rotated well before our intersection and were clear above us before passing our position next to the runway. I consider this occurrence to be entirely my fault. I should have come to a complete stop at the hold short line and scanned completely rather than a brief glance; no matter where I thought the other traffic on the airfield was. I should have avoided making non-critical radio calls in a sterile cockpit situation. I should have realized that students can and do make mistakes; and if the student really did call out runway xx mistakenly; I should have been aware that he could have made the call in error.I am usually the one to insist on proper adherence to sops and best practices. I am disappointed in myself and my performance today. Skill and professionalism; not luck; are what keep us safe. Today I was only lucky.
Original NASA ASRS Text
Title: A general aviation instructor pilot reported a critical ground conflict with another training aircraft on takeoff roll at a non-towered airport. Distraction and communication breakdown were cited as contributing factors.
Narrative: I was with a student taxiing to the active runway from the ramp. Another instructor was out on the airfield with his student; preparing to send him on his first solo. The AWOS indicated winds favoring Runway XX; so we made a radio call saying that we were taxiing to Runway XX. At that point; I communicated by radio with the other instructor about his student's upcoming first solo; a non-critical call that could have waited until the airplane was stationary (mistake number one). As we approached the hold short line for Runway YY; we slowed (but did not stop - mistake number two) and made a cursory scan for other aircraft left and right. We expected that the other instructor would be using Runway XX and so we failed to catch that he was actually beginning his takeoff roll on Runway YY (mistake number four). Whether his student actually called out Runway YY or XX is irrelevant; my student and I heard Runway XX and that's where our eyes were. We crossed the hold short line and were approaching the runway edge markings when we got an unreadable radio call; but which definitely contained the numbers Runway YY. We immediately stopped and looked to our right. Sure enough; the other aircraft was on the takeoff roll about to pass in front of us. They rotated well before our intersection and were clear above us before passing our position next to the runway. I consider this occurrence to be entirely my fault. I should have come to a complete stop at the hold short line and scanned completely rather than a brief glance; no matter where I thought the other traffic on the airfield was. I should have avoided making non-critical radio calls in a sterile cockpit situation. I should have realized that students can and do make mistakes; and if the student really did call out Runway XX mistakenly; I should have been aware that he could have made the call in error.I am usually the one to insist on proper adherence to SOPs and best practices. I am disappointed in myself and my performance today. Skill and professionalism; not luck; are what keep us safe. Today I was only lucky.
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.