General aviation pilot reported a near miss with another aircraft after takeoff from a non-towered airport in daylight visual conditions. The pilot reported the aircraft in sight and adjusted the climb to provide separation; then departed the traffic pattern.

2023-11 · NASA ASRS report 2054963

Date: 2023-11 · Aircraft: Small Aircraft; High Wing; 1 Eng; Fixed Gear · Phase: takeoff

Anomalies: conflict-ground-conflict|critical|deviation-discrepancy-procedural-published-material-policy|ground-incursion-runway

Synopsis

General aviation pilot reported a near miss with another aircraft after takeoff from a non-towered airport in daylight visual conditions. The pilot reported the aircraft in sight and adjusted the climb to provide separation; then departed the traffic pattern.

Narrative

I was holding short of Runway 25 at Iowa City waiting for the landing traffic before I departed. There were 3 other aircraft in the pattern; with Aircraft Y calling 3 miles to the North; intending to cross midfield and enter the left downwind for Runway 25. The next aircraft to land called abeam the numbers as Aircraft Y crossed midfield; reporting he did not have the landing traffic in sight. The landing traffic stated he would make a short approach to Runway 25; Aircraft Y then called midfield left downwind for Runway 25. At this point in time; I was holding short of Runway 25 and angled to see the final approach path. I saw the landing traffic on a short final; but did not see Aircraft Y; which had already turned its base; and its final. I made the mistake of assuming Aircraft Y was still on its downwind and had not turned base for Runway 25. Once the landing traffic passed the numbers; I made a radio call; announcing my intention to line up and wait for the landing traffic to conduct their touch and go. Upon pulling onto the Runway; I received a radio call from Aircraft Y stating they were on a short final and I had just cut them off. I decided to continue my take off roll; as I didn't believe putting the aircraft in the grass or merely sitting on the Runway was the best decision. I got an earful at that moment. I broadcast I had the departing traffic in sight ahead of me and Aircraft Y immediately at my 2 o'clock and about 100 feet above; and let him know I would stay low so he can turn his crosswind. I also informed him that I didn't hear his base of final radio calls and didn't see him on final. Aircraft Y informed me that he had made both radio calls and chastised me for not clearing final; which I had done but still didn't see him. Aircraft Y also felt it important to describe how difficult it is to perform a go-around in a turboprop aircraft and apologized for being curt with me. Its also important to note that I had ADSB on Foreflight on my IPAD. About the time I was pulling onto the Runway; I noticed an aircraft was on the downwind; at this time I cant say if that aircraft I saw on ADSB was Aircraft Y or not. After we had made sure we weren't going to hit one another; I departed straight out to get clear of the busy pattern. To correct myself in the future. Patience; and waiting for an actual visual of any aircraft intending to land; whether I hear radio calls from them or not. Another factor I will consider moving forward; is not relying on ADSB to verify where aircraft are in a busy pattern; whom I cant see due to the high wings. After departing the pattern; I sincerely apologized to all aircraft; gave my full N number; and cleared the area. I will continue to work with my instructor to correct this issue; and ensure this will not happen again. This has been nothing short of a humbling experience. If Aircraft Y hadn't been quick to react; conducted a go around; and broadcast his position; we both may not have made it. I did not attain Aircraft Y N number. If this story is published; it is my hope that the PIC of that aircraft sees this and knows how incredibly sorry I am for endangering his life.

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.