37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1746823 |
Time | |
Date | 202006 |
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 | SR22 |
Operating Under FAR Part | Part 91 |
Flight Phase | Final Approach |
Flight Plan | None |
Aircraft 2 | |
Make Model Name | M-20 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 91 |
Flight Plan | VFR |
Person 1 | |
Function | Instructor |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Instrument Flight Crew Multiengine |
Events | |
Anomaly | Conflict NMAC Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 100 Vertical 100 |
Narrative:
Two pilot training mission was launched out of ZZZ1-ZZZ2 in aircraft X then direct to ZZZ. The winds at ZZZ 010 @ 7 kts. We decided to land runway xx and enter right traffic as published. On approach; we did not see any other aircraft on TCAS. We made radio calls starting at 5NM west; to join midfield downwind after crossing midfield. We made additional radio calls with no response on the overhead; downwind; base; and final for runway xx. Upon turning final; we noticed nothing abnormal and continued the final decent. We entered the flare and during the flare; saw a landing light approaching on the centerline opposite direction on runway yy. We immediately began a go-around and offset to the east of the centerline and climbed out to rejoin the pattern missing the other aircraft by roughly 100 feet. Aircraft Y; that was on the runway did not make any known radio calls or take evasive action.additionally; at no point did we get a TCAS warning from our system.after landing; we made contact with the other pilot who explained he had the frequency input incorrectly into his radio and claimed to have been making calls without response.aircraft Y's lack of calls and long straight in approach over the lake instead of flying the pattern made them hard for us to spot.
Original NASA ASRS Text
Title: A SR22 Instructor Pilot reported a NMAC with opposite direction landing traffic at a non-towered airport.
Narrative: Two pilot training mission was launched out of ZZZ1-ZZZ2 in Aircraft X then Direct to ZZZ. The winds at ZZZ 010 @ 7 kts. We decided to land runway XX and enter right traffic as published. On approach; we did not see any other aircraft on TCAS. We made radio calls starting at 5NM West; to join midfield downwind after crossing midfield. We made additional radio calls with no response on the overhead; downwind; base; and final for runway XX. Upon turning final; we noticed nothing abnormal and continued the final decent. We entered the flare and during the flare; saw a landing light approaching on the centerline opposite direction on Runway YY. We immediately began a go-around and offset to the east of the centerline and climbed out to rejoin the pattern missing the other aircraft by roughly 100 feet. Aircraft Y; that was on the runway did not make any known radio calls or take evasive action.Additionally; at no point did we get a TCAS warning from our system.After landing; we made contact with the other pilot who explained he had the frequency input incorrectly into his radio and claimed to have been making calls without response.Aircraft Y's lack of calls and long straight in approach over the lake instead of flying the pattern made them hard for us to spot.
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.