The U.S. aircraft register, updated daily
Accidents · NTSB WPR22LA342 · Final report

Cessna 152 accident near Salt Lake City, Utah, September 7, 2022

On September 7, 2022 at about 9:00 pm local time, a 1979 Cessna 152, registered N48918, was substantially damaged in an accident during initial climb near Salt Lake City, Utah (South Valley Rgnl airport). It was an instructional flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The airplane’s encounter with a microburst during initial climb that resulted in a loss of altitude and subsequent collision with a tree.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 7, 2022 · about 9:00 pm local time
Place
Salt Lake City, Utah · South Valley Rgnl · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 152, built 1979 · all 152s on the register
Registration
N48918 · registry record · serial 15283389
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The flight instructor reported that, during an instructional flight with the student pilot at the flight controls, the airplane encountered a microburst during the takeoff climb. The airplane started to descend, he assumed control of the airplane, checked the engine RPM's and throttle. Despite his actions the airplane continued to descend. Unable to maintain altitude, he elected to land on a soccer field. During the landing roll, the right wing impacted a tree that resulted in substantial damage. Witnesses located near the accident location reported that, the accident airplane encountered a “microburst” and “big gust of wind,” and it then began/started to descend toward the ground. One witness stated that it appeared as if the airplane was “…fighting to gain altitude.” A Federal Aviation Administration inspector reported that, the accident flight was captured on airport surveillance camera, and showed the accident airplane take off in a normal climb profile. About 50-100 ft above ground level (agl), the airplane was seen making small abrupt changes in altitude, that the FAA inspector indicated was consistent with a turbulence encounter. As the airplane continued the climb, about 200-300 ft agl, it flew into a wall of vertical dust and appeared to be in a descent. The video showed the airplane as it continued forward in the dust while still in a descent until it was no longer visible in the video frame. Prior to the accident, the airport’s automated weather observation station reported that, at 14:55 local time, the wind was from 160° at 4 knots. Shortly thereafter, the same automated station reported that, at 15:15 local time, the wind was from 110° at 5 knots, gusting to 21 knots. The airplane was taking off from runway 16.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Off-field or emergency landing during emergency descent
  2. Windshear or thunderstorm during initial climb defining event

The NTSB's findings

  • Environmental issues › Conditions/weather/phenomena › Wind › Microburst › Effect on equipment
  • Aircraft › Aircraft oper/perf/capability › Aircraft capability › Climb capability › Attain/maintain not possible
  • Personnel issues › Task performance › Use of equip/info › Aircraft control › Instructor/check pilot

Flight instructor

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 480 hours in all; 167 in the last 90 days; 62 in the last 30 days; 428 as pilot in command; 150 on instruments
  • Medical certificate: Class 2 (without waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

Dual student

  • Certificate: student
  • Flight time: 13 hours in all; 13 in the last 90 days; 8 in the last 30 days
  • Medical certificate: Class 1 (with waivers/limitations)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Airframe total time: 4,394 hours
  • Last inspection: 100-hour inspection, July 28, 2022
  • Maximum gross weight: 1,670 lb
  • Seats: 2
  • Landing gear: fixed
  • Engine: Lycoming O-235-L2C (piston); 1,218 hours total

The flight

  • Flight plan: VFR
  • Runway 16, 5,800 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 110° at 5 knots, gusting 21
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 97°F (36°C), dew point 55°F (13°C)
  • Altimeter: 30.16 inHg
  • Observation at 3:15 pm from KU42

Weather report (METAR): KU42 072115Z AUTO 11005G21KT 10SM CLR 36/13 A3016 RMK AO1 T03620125

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

4 documents, released by the NTSB on December 9, 2022. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Other NTSB records under N48918 the same tail number, which may have belonged to a different aircraft at the time

1990-12-27BFO91LA021 · accident near South Boston, VA · destroyed · minor injuries
1987-01-23NYC87LA064 · accident near Simsbury, CT · substantial damage · no injuries

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.