FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX91LA185 · Cessna 182B

27 Apr 1991 · Arvin, CA, United States

Arvin Skydiving Center Cessna 182B · Accident: on ground/water collision with object during landing

Show on map Search Wikipedia NTSB source dataset
Report a problem

Event

NTSB case
LAX91LA185
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 182B

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
N7220E
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
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 collision with object
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 › Compensation for wind conditions, inadequate
  • Pilot in command › In-flight planning/decision, improper
  • Pilot in command › Proper touchdown point, not attained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

IN HIS WRITTEN STATEMENT, THE PILOT SAID THAT HE WAS ATTEMPTING A FULL STOP LANDING, BUT THE WIND DIRECTION AND VELOCITY CHANGED. HE EXECUTED A GO AROUND USING A CIRCLE TO LAND TECHNIQUE FROM AN ALTITUDE OF ABOUT 100 FEET ABOVE GROUND LEVEL. ON HIS SECOND APPROACH, THE AIRCRAFT TOUCHED DOWN ABOUT 1600 FEET FROM THE BEGINNING OF THE RUNWAY AND ABOUT 800 FEET FROM THE END OF THE RUNWAY. HE APPLIED FULL BRAKING, BUT THE AIRCRAFT EXITED THE END OF THE RUNWAY AND COLLIDED WITH A DIRT BERM. THE AIRCRAFT NOSED OVER AND CAME TO REST IN AN INVERTED POSITION.

Probable cause

1) THE PILOT INADEQUATELY COMPENSATED FOR WIND CONDITIONS; 2) THE PILOT'S IMPROPER INFLIGHT DECISION; AND 3) THE PILOT NOT ATTAINING THE PROPER LANDING TOUCHDOWN POINT.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX91LA185
Event ID
20001212X16824
Case number
LAX91LA185
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: 04cb8a6fa3c8b87bbdb1e2b7ea60edadec164ae7d69f746d4a0a7c2df5a57880; retrieved 2026-09-23T04:16:25.955Z.