LAX96LA178 · Cessna TR182
Cessna TR182 · Accident: loss of control on ground/water during landing
From Modesto City Co-Harry Sham Field (MOD) to Montgomery-Gibbs Executive Airport (MYF)
Event
- NTSB case
- LAX96LA178
- 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
- 0
- 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 TR182
- 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
- N737JE
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Modesto City Co-Harry Sham Field (MOD), Modesto, CATo Montgomery-Gibbs Executive Airport (MYF)
- 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
- Landing · landing roll
- 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
- Loss of control on ground/water
- 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 › Brakes(normal), excessive
- Pilot in command › Directional control, not maintained
- Pilot in command › Elevator, improper use of
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, the aircraft touched down without mishap. He indicated that during rollout he lost directional control of the airplane after allowing the yoke to come forward for taxiing off the runway. The airplane veered left, exited off the side of the runway, the nose gear separated, and the right wing contacted the ground. An inspection of the airplane revealed the nose gear assembly had sustained an overload type failure. No discrepancies were found with the operation of the brakes. The left main landing gear tire was noted to have flat spots on it. Several hundred feet of tire tread skid marks were observed on the runway which were consistent with the airplane's ground path.
Probable cause
the pilot's failure to maintain directional control during landing rollout as a result of his excessive application of brakes and improper use of the elevator (yoke) control.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA178
- Event ID
- 20001208X05621
- Case number
- LAX96LA178
- 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. 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: e44ede3e6f3df911a41b72387a34ad13f5ed7d59b1dc2e7fe6cdd5219d937b12; retrieved 2026-09-22T22:34:41.140Z.