1 Jul 2021: CESSNA 172R — Brian J. Makar

1 Jul 2021: CESSNA 172R (N2388L) — Brian J. Makar

2 fatalities • Missoula, MT, United States

Probable cause

The pilot’s failure to maintain airspeed and exceedance of the airplane’s critical angle of attack, which resulted in an aerodynamic stall at an altitude too low for recovery.

— NTSB Determination

Accident narrative

HISTORY OF FLIGHT On July 1, 2021, about 1149 mountain daylight time, a Cessna 172R airplane, N2388L, was substantially damaged when it was involved in an accident near Missoula International Airport (MSO), Missoula, Montana. The pilot and passenger were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot did not file a Federal Aviation Administration flight plan or inform family members of the airplane’s destination. Recorded air traffic control audio captured the pilot receiving a clearance for a departure on runway 26. The pilot read back the clearance. No additional communication between the pilot and the controller was recorded. Automatic dependent surveillance-broadcast (ADS-B) data captured the first 5 minutes 48 seconds of the flight. The data revealed that the airplane departed MSO about 1141 and proceeded on a southwesterly heading at a groundspeed of about 70 to 75 knots. About 3 minutes later, the airplane initiated a right turn onto a westerly heading toward the Grave Creek Mountain Range, climbed to an altitude of 3,850 ft mean sea level (msl), and maintained a groundspeed of about 70 to 75 knots. At 1143:56, the airplane’s groundspeed decreased to about 68 knots and remained at that speed until the end of the recorded data 3 minutes 23 seconds later. The last recorded ADS-B target, at 1147:19, showed that the airplane was at an altitude of 5,225 ft msl (678 ft above ground level), on a magnetic heading of 271°, and about 3.3 miles east of the accident site. See figure 1. The terrain elevation near the last ADS-B point was about 4,547 ft msl.

Figure 1. Overhead view of the flight track (in red) and the direction of travel (blue arrows). According to a ground support attendant at the fixed-base operator at the departure airport, the pilot requested that the fuel tanks be filled “all the way to the top.” The attendant reported that he added 28.5 gallons of fuel to the airplane. He stated that the pilot told him that he would be flying somewhere remote but did not specify where. AIRCRAFT INFORMATION The airplane’s weight for the flight was about 2,518 pounds. According to the Cessna 172R Pilot’s Operating Handbook, the maximum takeoff gross weight of the airplane was 2,450 pounds. The rate of climb, at maximum takeoff gross weight, at a pressure altitude of 6,000 ft and an airspeed of 74 knots was 415 ft per minute at 20°C and 360 ft per minute at 40°C. The stall speed for the flaps-up, power-off configuration was 51 knots calibrated airspeed. METEOROLOGICAL INFORMATION The density altitude for MSO about the time of the accident was calculated to be 5,917 ft. No SIGMET advisories for turbulence were active for the accident location at the accident time. No graphical AIRMET advisories (which are issued 3 hours apart) were active for the accident location at either 0900 or 1200 on the day of the accident. The Geostationary Operational Environmental Satellite-17 depicted mostly clear conditions across the region where the accident occurred. WRECKAGE AND IMPACT INFORMATION The airplane came to rest on a steep south-facing slope within a tree-covered canyon in the Grave Creek Mountain range (see figure 2) , on a magnetic heading of 040° and about 130° to the right of the last ADS-B data point. The valley was surrounded on three sides by higher elevation terrain.

Figure 2. Google Earth image showing the last ADS-B data point and the accident site. All terrain at or below 5,225 ft msl (the airplane’s altitude at the last data point) appears in yellow. The first identified point of impact was a severed tree trunk about 30 ft above ground level. Tree damage ahead of the wreckage was oriented from the south at a 30° to 45° angle. The terrain slope was about 45°.

All major components of the airplane were found in a small debris area immediately around the airplane, consistent with a lowenergy, nearvertical impact. According to the impact angle of the tree to the left wing, the airplane was about 30° nose down with little bank angle at the time of impact. Flight control continuity was established for all control surfaces. Postaccident examination of the airframe and engine revealed no mechanical malfunction or failures that would have precluded normal operation.

Contributing factors

  • Airspeed — Not attained/maintained
  • Capability exceeded
  • Pilot

Conditions

Weather
VMC, vis 10sm

Loading the flight search…

What you can do on Flight Finder

  • Search flights between any two airports with live fares.
  • By aircraft — pick a plane model (e.g. Boeing 787, Airbus A350) and see every route it flies from your origin.
  • Route map — click any airport worldwide to explore its destinations, or draw a radius to find nearby airports.
  • Global aviation safety — aviation accident database, 5,200+ records since 1980, with map and rankings by aircraft and operator.
  • NTSB safety feed — recent U.S. aviation accidents and incidents from the official NTSB CAROL database, updated daily.

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.