Ameriflight Flight AMF238
Piper PA-31-350 · Accident: hard landing
From Oakland San Francisco Bay Airport (OAK) to Fresno Yosemite International Airport (FAT)
Event
- NTSB case
- WPR09LA014
- 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
- Charter & commuter
- 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-31-350
- Aircraft type
- Piper PA-31
- 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
- N27996
- Operator
- Ameriflight
- Onboard fatalities
- Unknown
- Route
- From Oakland San Francisco Bay Airport (OAK), Oakland, CATo Fresno Yosemite International Airport (FAT), Fresno, 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 135: Air Taxi & Commuter
- 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
- Defining eventThe 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
- Aircraft › Aircraft oper/perf/capability
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that he made a firm landing and had a blown right main tire, but indicated no other problems. After replacement of both tires, the airplane continued in service for two flight sequences, flown by other pilots. Inspection by maintenance personnel revealed a line of popped rivet heads on the upper surface of the left wing above the rear spar between the nacelle and the wing fillet fairing. A close inspection discovered popped rivet heads on the left side of the fuselage below the cabin window with a gap visible in the skin lap. Inspection of both main gear wheels and tires revealed cuts and impressions in the tire sidewalls indicative of a very hard landing. Further inspection discovered buckling of both main spar webs between the fuselage and nacelles.
Probable cause
The pilot misjudged the flare resulting in a hard landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record WPR09LA014
- Event ID
- 20081016X64429
- Case number
- WPR09LA014
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: dd357bcbd64da686337b133a780930eaab16f50e1d143534ae5d052079cdb4b5; retrieved 2026-09-15T10:28:31.676Z.