# Accident 20030628012999A: Cessna 152, Las Vegas, NV, June 28, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: June 28, 2003, 15:30 local time
- Place: Las Vegas, NV
- Airport: North Las Vegas Air Terminal
- Damage: Destroyed
- Phase of flight: Fcd/Prec Ldg From Cruise
- Operating rules: General operating rules (Part 91)
- Location: 36.2578° N, 115.6489° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.2578&lon=-115.6489&mi=10
- Aircraft: N6182U, a cancelled registration (https://openairdocs.org/deregistered/N6182U-2003-10-08) (OpenAirDocs)
- Registry model: Cessna 152 (registry code 2071835, https://openairdocs.org/model/cessna-152) (OpenAirDocs)
- Registry engine: Lycoming 0-235 series (registry code 41505, https://openairdocs.org/engine/lycoming-0-235-series) (OpenAirDocs)
- Reported make and model: CESSNA 152
- Reported engine: LYC O235L2C
- Fatal injuries: 0
- Pilot flight hours: 6,100 total, 106 in this make and model, 5 in the last 90 days
- NTSB investigation: [NTSB LAX03LA214](https://openairdocs.org/ntsb/LAX03LA214) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030628012999A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(-23) PILOT WAS IN CANYON ATTEMPTING TO MAKE A 180 DEGREE TURN WHEN THE ENGINE LOST POWER AND THE AIRCRAFT LOST ALTITUDE. THE PILOT TRIED TO LAND ON A STATE ROAD, ROUTE 157, BUT WAS UNABLE TO. THE AIRCRAFT STRUCK A TELEPHONE POLE WITH THE LEFT WING, SPINNING THE AIRCRAFT 180 DEGREES AND LANDED IN A GROUP OF TREES FACING BACKWARDS. THERE WERE SEVERAL WITNESSES THAT HEARD THE ENGINE "SPUTTERING AND MISSING" AND SAW THE AIRCRAFT CRASH. THE AIRCRAFT STOPPED ABOUT 5 FEET FROM A HOUSE. THE OCCUPANTS OF THE HOUSE SPRAYED THE AIRCRAFT AND THE PILOT IMMEDIATELY UPON LANDING. SOME WITNESSES SAW AND HEARD THE AIRCRAFT AND FOLLOWED IT UNTIL IT CRASHED. THE PILOT WAS ABLE TO GET OUT OF THE AIRCRAFT BY HERSELF AND GET HELP FROM SEVERAL PEOPLE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX03LA214](https://openairdocs.org/ntsb/LAX03LA214), Jun 28, 2003: Cessna 152 (N6182U), Mt. Charleston, NV, substantial damage. Probable cause: the pilot's inadequate in-flight planning and selection of the wrong route of flight, which led the airplane toward rising terrain in excess of the performance capability of the airplane. Also causal…

## Other reports on N6182U (1)

Matched to the same aircraft by N-number and date.

- [Accident 19970612015179A](https://openairdocs.org/incident/19970612015179A), Jun 12, 1997: Cessna 152 (N6182U), Bridgeport, TX, Substantial damage. Became lost on cross country. Exhausted fuel. Struck rocks landing. Nosed over onto barbed wire fence. (-23) on June 12, 1997, at approximately 1626 CDT, a…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.