LAX86LA162 · Cessna 182J
Cessna 182J · Accident: on ground/water encounter with weather during landing
From Cavern City Air Terminal (CNM) to Flagstaff Pulliam Airport (FLG)
Event
- NTSB case
- LAX86LA162
- 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 182J
- 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
- N2691F
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Cavern City Air Terminal (CNM), Carlsbad, NMTo Flagstaff Pulliam Airport (FLG), Flagstaff, 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
- 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
- On ground/water encounter with weather
- 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 › Planning/decision, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE PLT SAID HIS WX BRIEFING INDCD VFR CONDS ALONG THE ROUTE WITH OCNL THUNDERSTORM (TSTM) ACTIVITY THAT MIGHT REQUIRE DIVERSION. AS HE WAS APCHG THE ST JOHNS ARPT, THE PLT SAW TSTMS & OVRCST CLDS AHEAD & DECIDED TO LAND & WAIT FOR THE WX TO IMPROVE. THE UNICOM OPERATOR ADVISED THAT THE WINDS FAVORED RWY 20 WITH A VELOCITY OF 20 GUSTING 25 KTS. THE PLT SAID THAT ON FINAL APCH, THE WINDS SHIFTED; HE NOTED THE 2 WINDSOCKS WERE SHOWING DIFFERENT DIRECTIONS. THE WINDSOCK AT THE INTERSECTION OF THE RWYS SHOWED A WIND FROM 270 DEG, FAVORING RWY 31. THE PLT LANDED NEAR THE CENTERLINE OF RWY 31. HE SAID HE WAS HOLDING CONTROLS FOR THE WIND WHEN A STRONG GUST GOT UNDER THE LEFT WING & PICKED IT UP. THE ACFT THEN RAN OFF THE RIGHT SIDE OF THE RWY, WENT INTO A DITCH & NOSED OVR. THE WIND DIRECTION METER IN THE ARPT TERMINAL WAS REPORTED TO BE INOP AT THE TIME THE PLT CALLED FOR HIS ARPT ADVISORY. THE DEMONSTRATED X-WIND COMPONENT FOR THE ACFT WAS 15 KTS.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX86LA162
- Event ID
- 20001213X33302
- Case number
- LAX86LA162
- 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: 6c137486a1a81c9077a7c3f6c1983bff8c2ef65244f2ff98eea979fb21e40dda; retrieved 2026-09-23T14:53:29.970Z.