37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 906552 |
Time | |
Date | 201008 |
Local Time Of Day | 0601-1200 |
Place | |
Locale Reference | GAI.Airport |
State Reference | MD |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | PC-12 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Route In Use | Visual Approach |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 91 |
Flight Phase | Landing |
Person 1 | |
Function | Pilot Flying Captain |
Qualification | Flight Crew Commercial Flight Crew Multiengine Flight Crew Flight Instructor Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 75 Flight Crew Total 5000 Flight Crew Type 5000 |
Events | |
Anomaly | Conflict NMAC |
Miss Distance | Horizontal 50 Vertical 50 |
Narrative:
Approximately 15 miles from the airport the first officer reported the airport in sight to potomac approach and were advised to change to advisory frequency. We were lined up for a straight in landing to runway 14. The weather was 6;000 ft scattered; the sun was shining; and we were in VFR conditions. The wind was reported as 3-5 kys from 300 degrees. The preferred calm runway is runway 14. We announced our position on the unicom frequency on four separate occasions. As we crossed the threshold for runway 14 at approximately 50 ft AGL; we both noticed a single engine airplane on runway 32 that appeared to be departing directly towards us and had just begun to rotate. I side-stepped to the right and initiated a go-around as the first officer called 'go-around.' we climbed to pattern altitude and began left traffic for runway 14. The other aircraft fell in behind us and also made left traffic to runway 14. Approximately halfway through the traffic pattern the pilot of the other airplane began to give position reports and landed behind us. We both landed uneventfully.once on the ground I was approached by the airport manager who had been informed of the incident by several airport employees. Together we confronted the other pilot. He claimed to have made several radio calls while in the pattern. The airport manager; line worker; and a customer service representative all confirmed that they had heard our radio calls; but none from the other pilot until after the go-around was initiated. The other pilot finally conceded that he must have been on the wrong frequency.
Original NASA ASRS Text
Title: A PC12 flight crew on short final to a non-towered airport initiated a go-around when confronted by an SR22 departing opposite direction on the same runway.
Narrative: Approximately 15 miles from the airport the First Officer reported the airport in sight to Potomac Approach and were advised to change to advisory frequency. We were lined up for a straight in landing to Runway 14. The weather was 6;000 FT scattered; the sun was shining; and we were in VFR conditions. The wind was reported as 3-5 KYS from 300 degrees. The preferred calm runway is Runway 14. We announced our position on the UNICOM frequency on four separate occasions. As we crossed the threshold for Runway 14 at approximately 50 FT AGL; we both noticed a single engine airplane on Runway 32 that appeared to be departing directly towards us and had just begun to rotate. I side-stepped to the right and initiated a go-around as the First Officer called 'go-around.' We climbed to pattern altitude and began left traffic for Runway 14. The other aircraft fell in behind us and also made left traffic to Runway 14. Approximately halfway through the traffic pattern the pilot of the other airplane began to give position reports and landed behind us. We both landed uneventfully.Once on the ground I was approached by the Airport Manager who had been informed of the incident by several airport employees. Together we confronted the other pilot. He claimed to have made several radio calls while in the pattern. The Airport Manager; Line Worker; and a Customer Service Representative all confirmed that they had heard our radio calls; but none from the other pilot until after the go-around was initiated. The other pilot finally conceded that he must have been on the wrong frequency.
Data retrieved from NASA's ASRS site as of April 2012 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.