 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
An instructor pilot reported entering the runway to depart causing an arriving aircraft on short final to go around.
| Attributes | |
| ACN | 1573537 |
| Time | |
| Date | 201808 |
| 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 | Visual Approach |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Flight Phase | Final Approach |
| Person 1 | |
| Function | Instructor |
| Qualification | Flight Crew Flight Instructor Flight Crew Commercial |
| Experience | Flight Crew Last 90 Days 227 Flight Crew Total 1425 Flight Crew Type 640 |
| Events | |
| Anomaly | Conflict Ground Conflict Critical |
| Miss Distance | Vertical 100 |
Narrative:
I was conducting an instructional flight. We were getting ready to enter the runway. Advisory had advised there was an aircraft on final approach; although I don't remember exactly how far out the aircraft was. I remember hearing at least 1 mile.we did our visual check to look for aircraft on base and final before entering the runway; and did not see anyone on final. The view from where the departure end of the runway makes it hard to see low flying aircraft because it sits below a berm; and then there is a building not far from the edge of the berm.because we did not see the approaching aircraft; and thought he was at least 1 mile out; we entered the runway and began the takeoff roll at which point the aircraft on final radioed that he was going around and executing a 180 degree climbing turn; and became very irate on the radio and requesting our tail number from advisory so he could report us. Advisory told him that they were not responsible for aircraft separation; and gave him the number for tower; and then I heard nothing else on the radio because we were well beyond the airspace for [the] airport.the traffic control system worked and we were advised about the aircraft; but having a less than desirable line of sight from the end of the runway to see low traffic was the cause of this incident.
Original NASA ASRS Text
Title: An instructor pilot reported entering the runway to depart causing an arriving aircraft on short final to go around.
Narrative: I was conducting an instructional flight. We were getting ready to enter the runway. Advisory had advised there was an aircraft on final approach; although I don't remember exactly how far out the aircraft was. I remember hearing at least 1 mile.We did our visual check to look for aircraft on base and final before entering the runway; and did not see anyone on final. The view from where the departure end of the runway makes it hard to see low flying aircraft because it sits below a berm; and then there is a building not far from the edge of the berm.Because we did not see the approaching aircraft; and thought he was at least 1 mile out; we entered the runway and began the takeoff roll at which point the aircraft on final radioed that he was going around and executing a 180 degree climbing turn; and became very irate on the radio and requesting our tail number from Advisory so he could report us. Advisory told him that they were not responsible for aircraft separation; and gave him the number for Tower; and then I heard nothing else on the radio because we were well beyond the airspace for [the] airport.The traffic control system worked and we were advised about the aircraft; but having a less than desirable line of sight from the end of the runway to see low traffic was the cause of this incident.
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.