Cessna 182A accident near Salt Lake City, Utah, July 1, 1999
On July 1, 1999 at about 10:06 pm local time, a Cessna 182A, registered N6165B, was substantially damaged in an accident near Salt Lake City, Utah (Salt Lake City Int'L airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
A total loss of engine power (nonmechanical) for reasons undetermined. Factors were the existence of conditions conducive to carburetor icing, and unsuitable terrain on which to make a forced landing.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 1, 1999 · about 10:06 pm local time
- Place
- Salt Lake City, Utah · Salt Lake City Int'L · map
- Type
- Accident
- Injuries
- No one was hurt; 1 person was on board or involved.
- Weather
- visual conditions (good weather)
- Aircraft
- Cessna 182A · all 182As on the register
- Registration
- N6165B · no longer on the register · serial 34165
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The pilot had been receiving vectors for spacing around traffic. When he was finally cleared to land, he was higher than traffic pattern altitude, and he slipped the airplane to dissipate excess altitude. When he advanced the throttle, the engine did not respond. An off-airport forced landing ensued. The airplane collided with a curb, stop sign, bus sign, and fence. The engine was later functionally tested and operated satisfactorily. It was the opinion of an FAA aviation safety inspector that the power loss may have been due to the engine 'loading up.' At the time of the accident, the airport temperature and dew point were 33 degrees C. (91.4 degrees F.) and 9 degrees C. (48.2 degrees F.), respectively. According to the Carburetor Icing Probability Curve, light icing at glide and cruise power settings are possible under these conditions.
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: private
- Ratings: single-engine land
- Flight time: 161 hours in all; 145 in this make and model; 20 in the last 90 days; 16 in the last 30 days; 114 as pilot in command
- Medical certificate: Class 3 (valid medical--no waivers/lim.)
- Seat: left
The aircraft
- Airframe total time: 3,500 hours
- Last inspection: annual inspection, May 30, 1999; 16 hours since
- Maximum gross weight: 2,650 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental O-470-L (piston); 0 hours total
The flight
- Departed from: 38U Loa UT at 8:30 pm
- Destination: SLC
- Flight plan: none
- Runway 32, 4,892 ft by 150 ft
Weather at the time
- Light: daylight
- Wind: from 360° at 9 knots
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 91°F (33°C), dew point 48°F (9°C)
- Altimeter: 29.00 inHg
- Observation at 10:20 pm from SLC
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Crew | 1 |
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.