NTSB CAROL · Event
Event CEN18LA087
Aircraft involved
Probable cause & findings
The airplane pilot’s failure to see and avoid the helicopter while in the traffic pattern, which resulted in a midair collision between the two aircraft. Contributing to the accident was the airplane pilot’s misunderstanding of the helicopter pilot’s intentions and the airplane pilot’s expectation that the helicopter would be clear of the runway.
Factual narrative
On January 26, 2018, about 1140 mountain standard time, a Robinson R44 II helicopter, N878BC, and a Beech A36 airplane, N777YF, collided while on approach to the Fort Collins-Loveland Municipal Airport (KFNL), Loveland, Colorado. The pilot in the helicopter sustained minor injuries and the pilot and passenger in the airplane were not injured. The helicopter was owned and operated by a private individual and the airplane was owned and operated by Landsgaard Equipment Leasing LLC. Visual metrological conditions prevailed at the time of the accident. The helicopter departed Century Helicopters Heliport (0CO7), Fort Collins, Colorado, at 1100, and the airplane departed the Greely-Weld County Airport (KGXY), at 1110. Both intended to land at KFNL.According to the helicopter pilot, when he approached KFNL, he announced on the common traffic advisory frequency, his intention to fly the RNAV GPS approach for runway 33. There was a National Guard UH60 helicopter flying the ILS 33 procedure. The pilots of the Guard helicopter intended to fly the ILS 33 to a missed approach, and then depart the area. The helicopter pilot informed them of his intention to perform the RNAV GPS 33 approach, perform the published missed approach procedures, and then enter the published holding pattern. He then heard the airplane pilot ask the UH60 if they intended to fly all the way to the end of the runway before turning east. They replied that they would be close to the end during the missed approach. The helicopter pilot continued the approach and the airplane pilot called that he was on the downwind, had the helicopter in sight, and would extend the downwind to give spacing. The helicopter pilot replied that he would fly the missed approach procedure and then return to the airport. The helicopter pilot heard the airplane pilot reply, "good." While descending towards the airport, the airplane pilot asked the helicopter pilot if he was stopping there, which the helicopter pilot replied that was still descending, and then intended to fly the missed approach. The airplane pilot then stated that he was passing overheard. Shortly after, the helicopter and the airplane collided. According to the airplane pilot, he approached KFNL from the east, and announced his initial position of 6-7 miles out. He heard other traffic conducting missed approaches and reported 2 miles and 1 mile out to coordinate with the local traffic. He announced crossing the field for the left downwind for runway 33 and proceeded into the pattern. While on the downwind leg for 33 and abeam the numbers he lowered the landing gear in preparation for landing. About that time the other pilot announced a straight in approach for 33, the airplane pilot saw that the aircraft was at a higher altitude, but he could see the aircraft was coming in on the approach approximately 4-5 miles out. On the radio, the airplane pilot offered to extend the downwind leg to allow the aircraft to complete its missed approach. On the base turn to final, the airplane pilot realized that the other aircraft was a helicopter and not an airplane. The helicopter continued its approach and when it was over the airport fence, the airplane turned onto final approach. About 4 miles south of the runway the airplane pilot said he could see the helicopter hovering south of the runway threshold, about ½ to ¾ mile from the end of the runway. He queried the helicopter pilot about his intentions, and he heard the helicopter pilot say that he was going to hover for a bit and then depart to the east. The airplane pilot replied "okay" and stated that he intended to fly over him for a full stop landing. The helicopter pilot responded "okay," so the airplane pilot proceeded to land on runway 33. During the approach, the airplane pilot lost sight of the helicopter. Expecting the helicopter to remain in a hover south of the runway, the airplane continued to land, descended, and collided with the helicopter. The helicopter descended, impacted terrain, and rolled on its right side resulting in substantial damage to the fuselage, and tailboom. After colliding with the helicopter, the airplane pilot saw the gear indicator show an unsafe right main landing gear. The airplane touched down on the left main landing gear and the pilot kept the right wing up for as long as possible. As the airplane slowed, the damaged right main touched down and the airplane departed the right side of the runway and came to rest in the adjacent grass. The responding Federal Aviation Administration Inspector auditioned audio from the UNICOM frequency. He did not hear the helicopter pilot transmit that he intended to hover. The airplane pilot stated that east of the runway 33/15 is where the local helicopter traffic usually performs their training, so he was expecting this helicopter to do the same. The accident occurred when a helicopter (N878BC) and an airplane (N777YF) collided midair while on approach to the airport. The helicopter pilot intended to fly a practice instrument approach to the runway, perform the missed approach procedure, and enter the published holding pattern. The airplane pilot intended to enter the traffic pattern, with appropriate spacing, for a full stop landing on the same runway. The airplane pilot had the helicopter in sight and was following the helicopter to the runway. While on final approach, the airplane pilot thought that the helicopter had entered a hover and asked the helicopter pilot about his intentions. The helicopter pilot indicated that he would be flying the missed approach procedure and then returning to the airport, but the airplane pilot incorrectly heard the helicopter pilot's response and believed that the helicopter was going to hover near the end of the runway and then proceed to the east. As a result, the airplane pilot expected the helicopter to be east of the airport, which was a common location for local helicopter training, when the airplane would be landing; however, the helicopter was on approach to the runway at that time. During the airplane's approach, the airplane pilot lost sight of the helicopter. The airplane continued to land and collided with the helicopter. Source: NTSB Aviation Accident Database Retrieved: 2026-02-12
NTSB Findings
Hierarchical cause / factor breakdown from the FAA bulk avdata database. Each finding tagged C (Cause) or F (Factor).
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot of other aircraft - C
- F Personnel issues-Action/decision-Info processing/decision-Expectation/assumption-Pilot of other aircraft - F
- F Personnel issues-Action/decision-Info processing/decision-Understanding/comprehension-Pilot of other aircraft - F
- C Personnel issues-Psychological-Attention/monitoring-Monitoring other aircraft-Pilot - C
- F Personnel issues-Action/decision-Info processing/decision-Expectation/assumption-Pilot - F
- F Personnel issues-Action/decision-Info processing/decision-Understanding/comprehension-Pilot - F
Verbatim from NTSB's published report. Source file
NTSB_2018_CEN18LA087.txt.
Findings + structured fields enriched from FAA avall.mdb.
Full investigation docket on
data.ntsb.gov ↗.
Beyond the agency record
Search this event elsewhere.
Pre-filled searches into the sources where news + community discussion of aviation events lives. External sources are reported, not agency. Treat them as signal that something happened, not as fact about what happened.
Entity-clustered aviation events in the press — last 24 hr + 30-day archive.
Official agency record + docket.
Investigative docket: factual reports, photos, transcripts.
Long-running aviation incident database (Flight Safety Foundation).
Community NTSB synthesis blog — often has photos and witness reports.
Gold-standard aviation incident blog.
Aviation industry news search.
GA pilot forum — informed but rumor-prone.
GA pilot subreddit search.
Tail-number page — flight history (free tier limited).
AOPA Air Safety Institute search.
Mainstream press coverage. Recent events only.
Privacy-preserving news search.
External links open in a new tab. We don't ingest their content; we deep-link search queries.
Related research
What the literature says.
Academic papers and agency reports matching this event's aircraft type or causal vocabulary (midair collision). Sourced from NASA NTRS, NTSB Safety Studies, FAA CAMI, AOPA Air Safety Institute, Embry-Riddle Scholarly Commons, arXiv, and the Semantic Scholar academic graph.
- Embry-Riddle Scholarly Commons 2024 · Journal article (IJAAA)
Airspace Saturation and Midair Collision Risk: A Case Study at a Class D Airport
Near midair collisions are precursor events to actual collisions and may be an indicator of risk. While previous studies have used reports of near midair collisions to relate factors such as airspace …
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for Urban Air Mobility (UAM)
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2023 · Presentation
The Viability of See-and-Avoid for Midair Collision Avoidance for UAM
Urban Air Mobility (UAM) is an emerging aviation concept that could supplement today’s ground and air transportation systems.
- NASA NTRS 2019 · Other - Patent
Apparatus for aiding a pilot in avoiding a midair collision between aircraft
An apparatus for aiding a pilot in avoiding a midair collision between aircraft is described. A protected aircraft carries a transmitter, a transponder, a receiver, and a data processor; and an intrud…
- Embry-Riddle Scholarly Commons 2018 · Journal article (IJAAA)
Evaluating Small UAS Near Midair Collision Risk Using AeroScope and ADS-B
As small unmanned aircraft systems (sUAS) continue to proliferate in the National Airspace System (NAS), near midair collisions are becoming more common.
- NASA NTRS 2011 · Reprint (Version printed in journal)
Midair collisions - The accidents, the systems, and the Realpolitik
Two midair collisions occurring in 1978 are described, and the air traffic control system and procedures in use at the time, human factors implications and political consequences of the accidents are …
Browse the full corpus — academia portal ↗