FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX99LA224 · Cessna 180K

16 Jun 1999 · Santa Monica, CA, United States

Cessna 180K · Accident: hard landing

From John Wayne Orange County International Airport (SNA) to Santa Monica Municipal Airport (SMO)

Report a problem

Event

NTSB case
LAX99LA224
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
N181RC
Operator
Unknown
Onboard fatalities
Unknown
Route
From John Wayne Orange County International Airport (SNA), Santa Ana, CATo Santa Monica Municipal Airport (SMO)
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 › Directional control, not maintained
  • Pilot in command › Flare, misjudged
  • Pilot in command › Ground loop/swerve, inadvertent

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

NTSB narrative

The pilot attempted to make a three point, full stall landing, but stalled the airplane about 1 foot above the runway. On touchdown the tail struck the runway and the airplane bounced back into the air. As the airplane continued to porpoise down the runway, the pilot added power and left rudder when a gust of wind caught the airplane from the right. The left wing tip struck the runway and the airplane ground looped.

Probable cause

The pilot's misjudged landing flare which resulted in a hard landing and the subsequent porpoising of the airplane; and his failure to maintain directional control that resulted in a ground loop and substantial damage to the airplane.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX99LA224
Event ID
20001212X19035
Case number
LAX99LA224
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: local date, investigation status. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 1999-06-17.
  • API snapshot SHA-256: a62cca15dee6aaeef7b293fbdbb52a58c90cb1ac79742c9b6f052bd864f50339; retrieved 2026-09-22T14:48:37.781Z.