FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX05CA043 · Piper PA-28-181

4 Dec 2004 · Santa Monica, CA, United States

Justice Aviation Piper PA-28-181 · Accident: overrun during landing

From Santa Monica Municipal Airport (SMO) to Santa Monica Municipal Airport (SMO)

Report a problem

Event

NTSB case
LAX05CA043
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
Unknown
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

Piper PA-28-181

Aircraft type
Piper PA-28
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
N253FD
Onboard fatalities
Unknown
Route
From Santa Monica Municipal Airport (SMO), Santa Monica, CATo Santa Monica Municipal Airport (SMO), Santa Monica, CA
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(cfi) › Compensation for wind conditions, inadequate
  • Pilot in command(cfi) › Remedial action, delayed
  • Pilot in command(cfi) › Supervision, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The airplane overran the runway and collided with a ditch during landing. The certified flight instructor (CFI) and student were on their last power-off approach. Approximately 2,500 feet down the 4,987-foot runway, the airplane continued to float. By the time it touched down, the CFI felt that it was too late to initiate a go-around procedure. The CFI applied the brakes, retracted the flaps, and turned the airplane to the right to avoid a ditch. An unedited surface weather observation (METAR) was issued for the airport about 20 minutes prior to the accident. The winds were reported from 070 degrees at 6 knots. The following METAR issued about 40 minutes following the accident reported winds from 100 degrees at 7 knots, with directional variations between 070 and 190 degrees. The CFI reported that she encountered no mechanical malfunctions with the airplane.

Probable cause

the certified flight instructor's inadequate supervision, inadequate compensation for the tailwind condition, and delayed remedial action, which resulted in a runway overrun and collision with a ditch.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX05CA043
Event ID
20041222X02024
Case number
LAX05CA043
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, coordinates. 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: 6e2e1036fba4f03013a8d292705838f3817100d8fce76d5efd0454fadfbba9e9; retrieved 2026-09-22T06:27:28.785Z.