LAX05LA126 · Piper PA-32-301T
Piper PA-32-301T · Accident: loss of control on ground/water during landing
From Santa Barbara Municipal Airport (SBA) to Long Beach International Airport (LGB)
Event
- NTSB case
- LAX05LA126
- 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-32-301T
- Aircraft type
- Piper PA-32
- 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
- N8243L
- Operator
- Meletios S. Berdelis · private individual
- Onboard fatalities
- Unknown
- Route
- From Santa Barbara Municipal Airport (SBA), Santa Barbara, CATo Long Beach International Airport (LGB), Long Beach, 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
- Loss of control on ground/water
- 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
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 veered off the runway and impacted signs during the landing rollout. The pilot reported that during the flight no mechanical malfunctions were experienced with his airplane, and he had performed a routine landing on runway 30. Within seconds after touchdown, the airplane veered left. The pilot attempted to straighten out the airplane's course, but he was not successful. The pilot also indicated that his loss of control surprised him, and his reaction time was slow. No vibration or shimmy was noted at any time during the landing rollout. Runway 30 is 10,000 feet long and 200 feet wide. At the time of the mishap, the surface wind was from 170 degrees at 5 knots. No other airplanes were in the area. The airplane's brake and steering systems were subsequently examined, and no evidence of any mechanical malfunction was found.
Probable cause
The pilot's failure to maintain directional control during the landing rollout.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX05LA126
- Event ID
- 20050404X00405
- Case number
- LAX05LA126
- 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: 891cce4fedad778f55d49efaddba22bb5f26cf153d1a6259bda9fb0dae6f9556; retrieved 2026-09-22T06:08:28.432Z.