LAX96LA182 · Cessna 402C
Cessna 402C · Accident: overrun during landing
From Phoenix Deer Valley Airport (DVT) to St Johns Industrial Air Park (SJN)
Event
- NTSB case
- LAX96LA182
- 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 402C
- Aircraft type
- Cessna 402
- 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
- N172VB
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Phoenix Deer Valley Airport (DVT), Phoenix, AZTo St Johns Industrial Air Park (SJN)
- 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
- Overrun
- 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 › Airspeed(vref), excessive
- Pilot in command › Compensation for wind conditions, inadequate
- Pilot in command › Distance/altitude, misjudged
- Pilot in command › Proper touchdown point, exceeded
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot decided to increase his final approach speed by 15 knots to compensate for the gust spread and crosswind. He descended on final approach using the VASI system as a glide path reference. After touchdown the airplane bounced and floated, and touched down again in the middle 1/3 of the 5,323-foot runway. The pilot did not notice how much runway was remaining. After clearing a slight rise, he saw the departure end of the runway and realized there was insufficient runway remaining to stop or execute a go-around. The airplane ran off the end of the runway. The AWOS recorded winds from 260 degrees at 33 knots gusting to 45 knots.
Probable cause
the pilot's inadequate compensation for the wind conditions, his use of an overly excessive approach speed, and his misjudged distance/altitude relationship to the runway. The wind was a factor.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX96LA182
- Event ID
- 20001208X05625
- Case number
- LAX96LA182
- 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: e8e65fa7950f661cb5b0553fa443d5b1edef4886e8ce861b26f2c98d63826386; retrieved 2026-09-22T22:38:58.157Z.