2024-11 · NASA ASRS report 2188077
Cessna pilot reported while on final approach taking evasive action to avoid a collision with another aircraft that was departing in the opposite direction.
I departed from ZZZ1 to ZZZ2 airport and decided to do a practice landing at ZZZ airport on the way to ZZZ2 airport.Surface winds at ZZZ1 airport were light and variable from the east to southeast based on windsock observation. I departed on runway XX. I used the weather observation at ZZZ3 airport for my altimeter setting.Approaching ZZZ I attempted to get updated weather information from the AWOS-2 on frequency; but did not hear any broadcast on that frequency. I did not observe any windsock movement; or detect any drift in my downwind flight pattern as I entered the left downwind for runway XY.As I was on final at approximately 500 feet above the ground I observed a yellow high wing aircraft departing from runway XZ. Each pilot turned to his/her right and there was no collision.I continued parallel to the runway southbound and departed the airport to the west to join the pattern for the left downwind to runway XZ. At this point I observed I had been transmitting my position reports on the wrong frequency. I changed to the correct frequency; made my position reports; and landed on runway XZ.While taxiing back to the approach end of XZ; the yellow high wing aircraft landed on runway XZ. His radio calls identified him as 'yellow high wing' and asked if I was the aircraft he had seen earlier. I said I was.I could not identify the make or model of the yellow high wing aircraft.I departed runway XZ and continued on to ZZZ2 airport where I landed.What could I have done differently?Surface winds at ZZZ2 were from the northeast at 5 kts which should have been a clue that other traffic in the area were landing/taking off to the north; not south. The wind was minimal at ZZZ but the reported wind at a nearby airport (26 miles away) might have been a better clue about which runway was in use.ZZZ does not report weather information on my EFB or through ADS-B. However the AWOS phone number does work.I should have double checked the radio frequency I was using to make my position reports when I did not hear any other aircraft transmitting. There was not much traffic this day so I was not surprised when the frequency was quiet.There is so much student training at airports in the area that radio congestion is usually a problem. But assuming that hearing no transmissions on a frequency meant that there was no aircraft in the pattern was a mistake.Neither the ADS-B or TCAS traffic detection alerted to show any traffic in the pattern. Radio transmissions from the yellow aircraft were given as 'yellow high wing' with no further information. But he flew his plane as expected so there was no collision.Since there is no requirement to make radio transmissions or have a transponder; I need to exercise more vigilance at uncontrolled airports; especially if there is not already an established traffic pattern in use.
Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.
Loading the flight search…
Pick an aircraft model — Boeing 737, Airbus A320, A380, Boeing 787 Dreamliner and more — enter your origin airport, and FlightFinder shows every route that plane flies from there with live fares.
We support Boeing 737/747/757/767/777/787, the full Airbus A220/A319/A320/A321/A330/A340/A350/A380 family, Embraer E170/E175/E190/E195, Bombardier CRJ and Dash 8, and the ATR 42/72 turboprops.
Search and schedules are free. Pro ($4.99/month, $39/year, or $99 one-time lifetime) unlocks the enriched flight card — on-time stats, CO₂ per passenger, amenities, live gate & weather — plus My Trips with push alerts.
Live schedules come from Amadeus, AeroDataBox and Travelpayouts. Observed routes (which aircraft actually flew a given city pair) are crowdsourced from adsb.lol ADS-B data under the Open Database License.