LAX90LA221 · Grumman G21A
Grumman G21A · Accident: hard landing
From an unrecorded airport to Long Beach, CA
Event
- NTSB case
- LAX90LA221
- 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
Grumman G21A
- Aircraft type
- Grumman G21
- 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
- N86640
- Operator
- Richard Probert
- Onboard fatalities
- Unknown
- Route
- From not recordedTo 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 · 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
- Flt control syst, elevator control cable/rod › Corroded
- Flt control syst, elevator control cable/rod › Stress corrosion
- Other maintenance personnel › Maintenance, inspection, inadequate
- Pilot in command › Gear retraction, not selected
- Pilot in command › Maintenance, annual inspection, not performed
- Pilot in command › Wheels down landing in water, inadvertent
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
DURING THE 18-MONTH PERIOD PRIOR TO THIS FLIGHT THE ACFT HAD BEEN REBUILT. THIS WAS THE FIRST FLIGHT TO LEAK-CHECK THE HULL BEFORE PAINTING. SEVERAL WATER LANDINGS WERE MADE; THE LAST BEING REFERRED TO BY A WITNESS 'IT HIT THE WATER'. THE PILOT STATED THAT WHILE RETURNING TO LONG BEACH ALL ELEVATOR CONTROL WAS LOST. HE ELECTED TO LAND BACK IN THE WATER, AND FORGOT THE WHEELS WERE DOWN. THE LANDING WAS MADE USING POWER AND ELEV TRIM, AND THE ACFT NOSED OVER NEAR THE SHORELINE. INVESTIGATION REVEALED A DISCOLORED & CORRODED ELEV CONTROL CABLE TURNBUCKLE THAT HAD FAILED DUE TO STRESS CORROSION CRACKING, WITH THE FINAL FAILURE MODE OF TENSILE OVERLOAD. THE PILOT STATED THAT HE HAD NOT MADE A WATER LANDING IN OVER ONE YEAR. ABOUT 2-1/2 HRS AFTER THE OCCURRENCE THE PILOT'S BLOOD ALCOHOL LEVEL WAS 0.022%.
Probable cause
THE PILOT'S FAILURE TO RETRACT THE LANDING GEAR RESULTING IN AN INADVERTENT WHEELS-DOWN LANDING IN WATER. IN ADDITION, A LOSS OF ELEVATOR CONTROL WAS ENCOUNTERED DUE TO A STRESS CORROSION FAILURE OF AN ELEVATOR CONTROL CABLE TURNBUCKLE AS A RESULT OF INADEQUATE MAINTENANCE AND INSPECTION. FACTORS WHICH CONTRIBUTED TO THE ACCIDENT WERE: A PREVIOUS HARD LANDING AS A RESULT OF AN IMPROPER LEVEL-OFF, AND THE PILOT'S LACK OF RECENT EXPERIENCE IN THE MAKE AND MODEL AIRPLANE.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX90LA221
- Event ID
- 20001212X23460
- Case number
- LAX90LA221
- Dataset
- historical-pre2008
- Source SHA-256
- 89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
- 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: 86e3fc232df930e55e439ae869e7987b26c5578533599d79e21a824f7ec74b62; retrieved 2026-09-21T15:41:21.445Z.
- Corrected after a review of the NTSB narrative, which states these values explicitly: destination. The narrative states the pilot lost elevator control "WHILE RETURNING TO LONG BEACH" and landed back in the water near the shoreline at Long Beach, CA; the destination was not recorded.