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

Cessna 172 accident near West Jordan, Utah, February 24, 1996

On February 24, 1996 at about 9:20 pm local time, a Cessna 172, registered N76027, was destroyed in an accident near West Jordan, Utah (Salt Lake City Muni No. 2 airport). It was an instructional flight under general aviation rules (Part 91). 1 person had minor injuries; 2 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

improper installation of the airplane's carburetor fuel lines by maintenance personnel.

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

What the record shows

Date
February 24, 1996 · about 9:20 pm local time
Place
West Jordan, Utah · Salt Lake City Muni No. 2 · map
Type
Accident
Injuries
1 person had minor injuries; 2 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Cessna 172 · all 172s on the register
Registration
N76027 · no longer on the register · serial 17268095
Damage
Destroyed
Flight
Instructional flight · general aviation rules (Part 91)

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

While climbing out after takeoff on an instructional flight, the engine began to 'run rough.' The CFI elected to return to the airport. While on final approach, the engine lost all power. The airplane landed uneventfully and stopped on the runway. The CFI reported that he then attempted to restart the engine so that he could clear the runway for incoming traffic. While starting the engine, the engine compartment caught fire. The airplane continued to burn until it was destroyed. An inspection of the wreckage revealed that the main fuel line to the finger strainer in the carburetor was disconnected with no mechanical damage noted. No other lines were disconnected. The fuel line had been installed by a mechanic eight days prior to the accident during a maintenance check.

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

Pilot

  • Certificate: flight instructor, commercial pilot
  • Ratings: single-engine land; instructor: airplane single-engine; instrument: airplane
  • Flight time: 789 hours in all; 44 in this make and model; 120 in the last 90 days; 40 in the last 30 days; 724 as pilot in command; 435 on instruments
  • Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
  • Seat: left

The aircraft

  • Airframe total time: 2,086 hours
  • Last inspection: 100-hour inspection, January 5, 1996; 43 hours since
  • Maximum gross weight: 2,400 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360-H2AD (piston); 0 hours total
  • Fire on the ground

The flight

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

Weather at the time

  • Light: daylight
  • Wind: from 160° at 16 knots
  • Visibility: 15 statute miles
  • Sky: overcast at 20,000 ft; scat at 14,000 ft
  • Temperature: 55°F (13°C), dew point 23°F (-5°C)
  • Altimeter: 29.00 inHg
  • Observation at 9:53 pm from SLC

Injuries

FatalSeriousMinorNone
Crew11
Passengers1

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

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.