37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1692303 |
Time | |
Date | 201910 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | CCO.Airport |
State Reference | GA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | DA42 Twin Star |
Operating Under FAR Part | Part 91 |
Flight Phase | Taxi |
Aircraft 2 | |
Make Model Name | Vans Aircraft Undifferentiated or Other Model |
Flight Phase | Landing |
Person 1 | |
Function | Instructor Pilot Not Flying |
Qualification | Flight Crew Instrument Flight Crew Flight Instructor Flight Crew Commercial Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 300 Flight Crew Total 1150 Flight Crew Type 382 |
Events | |
Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy Ground Incursion Runway |
Miss Distance | Horizontal 7000 Vertical 600 |
Narrative:
It was a training flight with a student. We finished run-up and taxied to the hold short line of runway 14 on [taxiway] B1. Runway 32 was in use so we scanned for potential traffic. The only traffic was aircraft Y midfield downwind. I instructed the student to cross from [taxiway] B1 to A1 on the departure end of runway 32; on the ground. The student made the radio call and we began to cross. Suddenly we heard radio calls coming from aircraft Y who was suddenly on final at about 600 ft. AGL. We were surprised because this plane had not been making radio calls except to announce he was on downwind. The student froze with confusion. At this point we were already on the runway so instructed the student to hurry and finish crossing the runway to get out of the way of aircraft Y. Aircraft Y was then at 400 ft. AGL and continued to yell at us. Aircraft Y went around and everything was fine.I think this could've been avoided if aircraft Y had made better/ more frequent radios call; if he had flown a normal traffic pattern; or if he had announced he was making a short approach. We would not have entered the runway if we knew a plane was on base or final.
Original NASA ASRS Text
Title: Flight instructor reported entering a runway while another aircraft was on final; resulting in a ground conflict and a go-around.
Narrative: It was a training flight with a student. We finished run-up and taxied to the hold short line of Runway 14 on [Taxiway] B1. Runway 32 was in use so we scanned for potential traffic. The only traffic was Aircraft Y midfield downwind. I instructed the student to cross from [Taxiway] B1 to A1 on the departure end of Runway 32; on the ground. The student made the radio call and we began to cross. Suddenly we heard radio calls coming from Aircraft Y who was suddenly on final at about 600 ft. AGL. We were surprised because this plane had not been making radio calls except to announce he was on downwind. The student froze with confusion. At this point we were already on the runway so instructed the student to hurry and finish crossing the runway to get out of the way of Aircraft Y. Aircraft Y was then at 400 ft. AGL and continued to yell at us. Aircraft Y went around and everything was fine.I think this could've been avoided if Aircraft Y had made better/ more frequent radios call; if he had flown a normal traffic pattern; or if he had announced he was making a short approach. We would not have entered the runway if we knew a plane was on base or final.
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.