FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX89LA075 · Piper PA-28-161

29 Dec 1988 · Avalon, CA, United States

Aviation Clubs of Fullerton Piper PA-28-161 · Accident: overrun during landing

From Jack Northrop Field Hawthorne Municipal Airport (HHR) to an unrecorded destination

Report a problem

Event

NTSB case
LAX89LA075
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

Piper PA-28-161

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
N28843
Onboard fatalities
Unknown
Route
From Jack Northrop Field Hawthorne Municipal Airport (HHR), Hawthorne, CATo 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
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 › Airspeed, excessive
  • Pilot in command › Planned approach, improper

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

NTSB narrative

THE PILOT LOST CONTROL OF THE AIRPLANE DURING LANDING ROLL AT CATALINA AIRPORT. THE AIRPLANE DEPARTED THE END OF RUNWAY 22, WENT DOWN A STEEP SLOPE AND COLLIDED WITH THE GROUND. THE PILOT REPORTED THAT HIS FIRST APPROACH HAD BEEN TOO HIGH, SO HE MADE A GO-AROUND AND RETURNED FOR LANDING. THE PLT SAID HE THEN MADE A NORMAL APPROACH AND LANDED 200-300 FEET PAST THE RUNWAY THRESHOLD. HE STATED THAT, 'I APPLIED NORMAL AND EVEN BRAKING PRESSURE, BUT THE PLANE DID NOT RESPOND AS I EXPECTED. INSTEAD IT DECELERATED VERY SLOWLY.' A WITNESS STATED THAT THE AIRPLANE TOUCHED DOWN IN THE LAST THIRD OF THE RUNWAY; HE STATED THAT THE PILOT'S APPROACH SEEMED TO BE FASTER THAN NORMAL. THE PILOT REPORTED NO MECHANICAL MALFUNCTIONS OR FAILURES OF THE AIRPLANE.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record LAX89LA075
Event ID
20001213X27451
Case number
LAX89LA075
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: 2d8137c448f5fa4f1b16564974284ed52f41d10df2a0c116714df8c7a1b551b3; retrieved 2026-09-22T00:18:59.282Z.