LAX94LA305 · Cessna 172N
Cessna 172N · Accident: hard landing
From Sacramento Executive Airport (SAC) to an unrecorded destination
Event
- NTSB case
- LAX94LA305
- 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
Cessna 172N
- Aircraft type
- Cessna 172
- 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
- N739RF
- Operator
- Marty Keane
- Onboard fatalities
- Unknown
- Route
- From Sacramento Executive Airport (SAC), Sacramento, 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 · 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
- Pilot in command › Elevator, improper use of
- Pilot in command › Flare, improper
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot stated that he came in high over the runway numbers with full flaps and maintained his descent attitude until he began to flare and reduce his airspeed. He stated that he inexplicably pushed forward on the control wheel to get the aircraft on the ground. On initial touchdown, the aircraft bounced back into the air. The pilot again attempted to flare and bounced once again about 10 or 15 feet in the air. On the third attempted landing, the aircraft remained on the runway after touchdown. The pilot reported that after turning off the runway onto the taxiway, the aircraft became difficult to taxi. He said he attributed the difficulty to the fact that his destination on the airport required him to taxi uphill. An inspection of the aircraft revealed that the nosewheel tire was blown, the nose wheel strut was broken at the top attachment point, and the engine firewall was buckled.
Probable cause
the pilot's improper use of the elevator control during the landing flare.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX94LA305
- Event ID
- 20001206X01797
- Case number
- LAX94LA305
- 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: 5c5e264bc292b91be29c82435f0bee5bc770863c0bd0462c1ef90d3526eea01a; retrieved 2026-09-23T00:52:24.989Z.