 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Beech 99 captain reported that selecting the incorrect CTAF frequency resulted in a critical ground conflict.
| Attributes | |
| ACN | 1741166 |
| Time | |
| Date | 202004 |
| Local Time Of Day | 0001-0600 |
| Aircraft 1 | |
| Make Model Name | Airliner 99 |
| Flight Phase | Takeoff |
| Route In Use | None |
| Flight Plan | VFR |
| Person 1 | |
| Function | Captain |
| Qualification | Flight Crew Private Flight Crew Multiengine Flight Crew Commercial |
| Events | |
| Anomaly | Conflict Ground Conflict Critical Deviation - Procedural Published Material / Policy |
Narrative:
I was just doing my normal thing once I was unloaded at ZZZ. On my way to ZZZ1 taxiing via [taxiway] a for departure and was transmitting my intentions. For example; taxiing for departure runway 35; it will be a north bound departure; ZZZ traffic. I heard nothing on frequency which is pretty common and not unusual. Setting torque once lined up on runway 35; I initiated my takeoff roll only to see another aircraft landing or departing (couldn't tell) runway 30. What the heck! Why weren't they on frequency? It was smaller GA traffic though; so I was not surprised. I had to delay my rotation just to ensure I would not take off into their belly. I would call this a near miss. Once on the ground at ZZZ1 a local airport man rode up to my plane on a tractor looking thing while loaders were offloading. He asked what frequency I was on. I said [frequency]. He said frequency is [frequency]. I was appalled at what had happened and extremely embarrassed. I later apologized to the other aircraft doing pattern work there on the correct frequency. Always double check frequencies. If you don't hear anything check your frequency or talk to the previous approach frequency to try to get traffic advisories.
Original NASA ASRS Text
Title: Beech 99 Captain reported that selecting the incorrect CTAF frequency resulted in a critical ground conflict.
Narrative: I was just doing my normal thing once I was unloaded at ZZZ. On my way to ZZZ1 taxiing via [Taxiway] A for departure and was transmitting my intentions. For example; taxiing for departure Runway 35; it will be a north bound departure; ZZZ traffic. I heard nothing on frequency which is pretty common and not unusual. Setting torque once lined up on Runway 35; I initiated my takeoff roll only to see another aircraft landing or departing (couldn't tell) Runway 30. What the heck! Why weren't they on frequency? It was smaller GA traffic though; so I was not surprised. I had to delay my rotation just to ensure I would not take off into their belly. I would call this a near miss. Once on the ground at ZZZ1 a local airport man rode up to my plane on a tractor looking thing while loaders were offloading. He asked what frequency I was on. I said [frequency]. He said frequency is [frequency]. I was appalled at what had happened and extremely embarrassed. I later apologized to the other aircraft doing pattern work there on the correct frequency. Always double check frequencies. If you don't hear anything check your frequency or talk to the previous approach frequency to try to get traffic advisories.
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.