General aviation pilot reported a near miss with a helicopter while entering the traffic pattern at a non-towered airport. The pilot did not follow normal published traffic pattern entry procedures and created the traffic conflict; then landed normally.

2024-05 · NASA ASRS report 2124395

Date: 2024-05 · Aircraft: Small Aircraft; Low Wing; 1 Eng; Retractable Gear · Phase: approach

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

Synopsis

General aviation pilot reported a near miss with a helicopter while entering the traffic pattern at a non-towered airport. The pilot did not follow normal published traffic pattern entry procedures and created the traffic conflict; then landed normally.

Narrative

I was released from my IFR flight plan for a visual approach and was told to squawk VFR and change frequency. I made position calls beginning at about 10 miles south of the airport. I heard there was a helicopter using Runway 16. I announced that I was descending from 4;000 ft and was 10 miles from the airport and will enter left downwind for Runway 16. The helicopter was making good position calls; but I was never able to find him. It wasn't until I was very near the airport that I realized I was lining up for Runway 03 instead of Runway 16 and that my 45-degree entry intention was skinny. I realized I was over the departure end of Runway 16; still a little high for pattern altitude; so I immediately turned wide for the downwind on the real Runway 16. I landed normally and didn't see the helicopter (he was on right downwind for RWY 16 at this time) until I turned base for Runway 16. The helicopter pilot gave me his phone number for me to text him so he could call me after he landed; which he did. He said we came too close was he was on the upwind for Runaway 16 and that I should never cross over the departure end while entering a pattern. I explained my error and I discussed what I should have done better. After being released from IFR; I should have swung wider to enter left downwind for RWY 16 on a more accurate 45-degree angle. Even with the error I made today in mistaking RWY 03 for RWY 16; if my entry angle to the pattern were better; I would not have crossed over the departure end of RWY 16 as I had done mistakenly.

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.