FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

LAX06CA167 · Cessna 310N

2 Apr 2006 · Lincoln, CA, United States

Cessna 310N · Accident: gear collapsed during landing

From Sacramento International Airport (KSMF) to Lincoln Regional Karl Harder Field (KLHM)

Report a problem

Event

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

Cessna 310N

Aircraft type
Cessna 310
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
N5096Q
Onboard fatalities
Unknown
Route
From Sacramento International Airport (KSMF), Sacramento, CATo Lincoln Regional Karl Harder Field (KLHM), Lincoln, 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
Gear collapsed
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

  • Landing gear, gear locking mechanism › Worn
  • Other maintenance personnel › Maintenance, inspection, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While transitioning from landing to taxiing the pilot experienced a bumping sound, which was followed by the collapse of the nose gear. Examination of photographs of the damage revealed that several inches of the nose fuselage structure had been ground down by contact with the runway pavement. The nose gear was examined by an airframe and power plant (A&P) mechanic. The mechanic reported that the nose gear drive tube was bent inboard 90 degrees, suggesting that the nose over center adjustment was out of tolerance, and a sufficient impact could cause the gear to unlock from the down position. There was no evidence of mechanical failure or foreign object damage.

Probable cause

The collapse of the nose gear due to an out of tolerance nose gear over center adjustment.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record LAX06CA167
Event ID
20060620X00777
Case number
LAX06CA167
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2006-04-03.
  • API snapshot SHA-256: ae6e22bc3afda1d2c241bc5e4c3d6a775ee4e28f40bf6da50d2aeedbdc042312; retrieved 2026-09-22T05:01:56.731Z.