A near miss was reported near S27 in spite of three involved aircraft making proper CTAF reports.

2011-08 · NASA ASRS report 964063

Date: 2011-08 · Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear · Phase: approach

Anomalies: conflict-nmac|deviation-discrepancy-procedural-published-material-policy

Synopsis

A near miss was reported near S27 in spite of three involved aircraft making proper CTAF reports.

Narrative

This morning I departed S27 flew over the nearby mountains and returned across 'lower valley' toward S27; slowing descending to pattern altitude of 3;800 MSL. Approximately four to five miles southeast of S27; I heard an aircraft calling Kalispell City; 'five to the west;' altitude unknown. I then reported my position; 'three to four to the southeast; over the river; inbound for landing; will be entering a left downwind for Runway 13.' At this time a third aircraft reported 'inbound for landing; will keep an eye out for you once I find him.' My course was a forty five degree intercept to left downwind; as reported; and offered a geographic reference as well; 'over the river.' I then reported to both aircraft that I was entering a left downwind for 13; and was nearly to the radio towers southeast of the field. Suddenly my passenger and I noted a red and white aircraft climbing; banking toward us; and taking evasive maneuvers with a turn to the pilot's right. I immediately banked right as well; passing perhaps within 300 FT horizontally of this third aircraft. Based on my position reports; it remains unclear to me why he was in this area; seemingly flying the pattern backward and/or on an intercept to inbound standard left pattern traffic. Now established on the left downwind for 13; I noted the sock was slightly favoring 31. I reported this; and indicated I would be crossing midfield to enter a left downwind for 31. The initial pilot was in sight; and he was in a more favorable position to land first. As such; we both communicated; and I indicated I would land 'number two' and extended by left downwind appropriately. The red and white aircraft that nearly intercepted us reported that he would be 'number three; both inbound aircraft in sight.' After landing; we taxied to the FBO. The third aircraft taxied the length of the runway before returning to 31 to depart. To answer the question as to what I might have done differently; I would have reported my position at five miles; rather than three to four miles. With two clear position reports and a geographic reference; I do not believe that other pilots familiar with S27 would have strayed toward the most common inbound arrival pattern.

Source: NASA Aviation Safety Reporting System (public domain). Reports are voluntary submissions and are not verified by NASA.

Loading the flight search…

Frequently asked questions

How do I search flights by aircraft type on FlightFinder?

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.

Which aircraft types can I filter by?

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.

Is FlightFinder free to use?

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.

Where does the route data come from?

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.