LAX02LA181 · Cessna 182P
Cessna 182P · Accident: airframe, component or system failure en route
From Prescott Regional Airport - Ernest A. Love Field (PRC) to Tucson International Airport (TUS)
Event
- NTSB case
- LAX02LA181
- Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
- Accident
- InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
- Completed
- API-reported fatalities
- 0 · all aircraft and ground
- Ground fatalities
- Unknown
- OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
- General aviation
- WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
- Visual Meteorological Cond
Cessna 182P
- Aircraft type
- Cessna 182
- Category
- Airplane
- RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
- N79107
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Prescott Regional Airport - Ernest A. Love Field (PRC), Prescott, AZTo Tucson International Airport (TUS), Tucson, AZ
- Aircraft age
- Not recorded
- Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
- Part 91: General Aviation
- Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
- En route · cruise
- First occurrenceThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
- Airframe, component or system failure
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Substantial
Cause areas
- Pilot in command › Aircraft control, not maintained
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
During the landing rollout, the airplane veered to the left of the runway and struck trees. The pilot made a precautionary landing after experiencing a complete loss of electrical power. There were no mechanical or electrical discrepancies noted with the first portion of the cross-country flight. During the return trip, center controllers had a hard time receiving radio transmissions from the pilot. The precautionary landing was initiated due to the vicinity of a mountain range that the pilot did not want to traverse to return to home base. The before landing checklist was performed. On base, the pilot selected 20 degrees of flaps, and noted the airspeed at 100 mph. On final, full flaps were selected. The pilot indicated that he did not believe the flaps were down. On short final a visual observation verified that the flaps were not deployed. The decision was made to land instead of attempting a go-around. During the landing rollout, the pilot did not brake evenly and the airplane veered to the left impacting trees. The brake system was inspected with no mechanical anomalies noted.
Probable cause
Failure of the pilot to maintain aircraft control during the landing rollout after making a precautionary landing precipitated by an electrical system failure.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX02LA181
- Event ID
- 20020606X00815
- Case number
- LAX02LA181
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (4)
- Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
- Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
- The date is the local date, which is the same as the UTC date the NTSB stores.
- API snapshot SHA-256: a69176f2476279f63f0793689839e5c5c52205c1865b3a62f3c63f59aedb0c33; retrieved 2026-09-22T10:53:48.233Z.