LAX83LA361 · Cessna 180K
Cessna 180K · Accident: hard landing
From U42 · Salt Lake City, UT to Oceanside Municipal Airport (OCN)
Event
- NTSB case
- LAX83LA361
- 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 180K
- Aircraft type
- Cessna 180
- 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
- N2572K
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From U42 · Salt Lake City, UTTo Oceanside Municipal Airport (OCN), Oceanside
- 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 · flare/touchdown
- 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
- Hard landing
- 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 › Flare, improper
Approximate · Estimated position: the centre of Las Vegas, NV, the place the record names. Not the accident site.
NTSB narrative
THE PLT REPORTED THAT DURING TOUCHDOWN, HE HEARD A LOUD SQUEAL FROM A TIRE & FELT THE AIRCRAFT PULL TO THE LEFT. HE STATED THAT HE APPLIED RIGHT AILERON & RUDDER TO KEEP THE ACFT GOING STRAIGHT. HOWEVER, AS THE ACFT SLOWED, IT BEGAN TO VEER LEFT AGAIN. HE SAID THE LEFT TIRE THEN LITERALLY EXPLODED. THE LEFT GEAR STRUT COLLAPSED & THE PROP & LEFT WING TIP CONTACTED THE RUNWAY. THE ACFT THEN VEERED TO THE RIGHT & WENT OFF THE RWY. HOWEVER, THE AIR TRAFFIC CONTROL SPECIALISTS WORKING LOCAL & GROUND CONTROL SAID THEY OBSERVED THE ACFT LAND HARD WITH THE LEFT WING DOWN, BOUNCE ONTO ITS LEFT GEAR, COME BACK DOWN ON THE RWY & DEPART THE RWY AS THE WHEEL SEPARATED. AN EXAM REVEALED THE LEFT MAIN TIRE WAS TORN OR RIPPED ACROSS THE TREAD, SIDEWALL & BOTH BEADS. THE INNER TUBE SHOWED SIMILAR DAMAGE. NO FLAT SPOTS WERE NOTED. THE WHEEL ASSEMBLY WAS FRACTURED & BROKEN, BUT NO PRE-FRACTURE EVIDENCE OF DEFECTS WAS NOTED.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record LAX83LA361
- Event ID
- 20001214X43829
- Case number
- LAX83LA361
- 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: 7f4036558c0efdb2978e0eb3f2e25110793dbf6b64229640eb3d9abece796321; retrieved 2026-09-23T21:41:04.368Z.