 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Pilot reported a critical ground conflict with opposite landing aircraft; determined later to be using the wrong CTAF frequency.
| Attributes | |
| ACN | 1739994 |
| Time | |
| Date | 202004 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZZZ.Airport |
| State Reference | US |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | PC-12 |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Flight Plan | VFR |
| Aircraft 2 | |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Landing |
| Flight Plan | None |
| Person 1 | |
| Function | Captain Pilot Flying Single Pilot |
| Qualification | Flight Crew Private Flight Crew Instrument |
| Experience | Flight Crew Last 90 Days 7 Flight Crew Total 2900 Flight Crew Type 1600 |
| Events | |
| Anomaly | Conflict Ground Conflict Critical Ground Incursion Runway |
Narrative:
The CTAF frequency was quiet; and I announced that I was taking runway 24 for takeoff. Just before entering the runway; I looked; but did not see any aircraft approaching for either runway. During the takeoff roll; the airport manager noticed another aircraft landing on the opposite runway 6; and alerted me on the CTAF frequency. It was only then that I noticed the aircraft.fortunately; that aircraft was on the ground and stopping; and I was ready to rotate; which I did; missing the other aircraft on the ground. In speaking to the airport manager later; he informed me that he had spoken to the other pilot; who had said that I wasn't on the frequency. After the airport manager informed him that I was on the frequency; and that it was he that wasn't on the frequency; they checked his radio and discovered that he was indeed on a different frequency by mistake.the lesson learned for me is just to reinforce that seeing approaching aircraft can be quite difficult; especially when they are on final with a cluttered background. Therefore; especially at uncontrolled airports; it is vital to use extra caution to ensure there are no aircraft approaching before entering the runway; and then to focus more than normal attention to such on the takeoff roll as well.
Original NASA ASRS Text
Title: Pilot reported a critical ground conflict with opposite landing aircraft; determined later to be using the wrong CTAF frequency.
Narrative: The CTAF frequency was quiet; and I announced that I was taking runway 24 for takeoff. Just before entering the runway; I looked; but did not see any aircraft approaching for either runway. During the takeoff roll; the airport manager noticed another aircraft landing on the opposite runway 6; and alerted me on the CTAF frequency. It was only then that I noticed the aircraft.Fortunately; that aircraft was on the ground and stopping; and I was ready to rotate; which I did; missing the other aircraft on the ground. In speaking to the airport manager later; he informed me that he had spoken to the other pilot; who had said that I wasn't on the frequency. After the airport manager informed him that I was on the frequency; and that it was he that wasn't on the frequency; they checked his radio and discovered that he was indeed on a different frequency by mistake.The lesson learned for me is just to reinforce that seeing approaching aircraft can be quite difficult; especially when they are on final with a cluttered background. Therefore; especially at uncontrolled airports; it is vital to use extra caution to ensure there are no aircraft approaching before entering the runway; and then to focus more than normal attention to such on the takeoff roll as well.
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.