# Incident 19990216001399I: Cessna 310F, Livermore, CA, February 16, 1999

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: February 16, 1999, 18:00 local time
- Place: Livermore, CA
- Airport: Livermore Municipal Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 37.6934° N, 121.8204° W: Placed by OpenAirDocs at LIVERMORE MUNI (LVK), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=37.6934&lon=-121.8204&mi=10
- Aircraft: N5833X, registered now (https://openairdocs.org/aircraft/N5833X) (OpenAirDocs)
- Registry model: Cessna 310F (registry code 2074216, https://openairdocs.org/model/cessna-310f) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 310F
- Reported engine: CONT IO470D
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 15,000 total, 800 in this make and model, 10 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19990216001399I

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

ACFT LANDED GEAR UP. THE STATEMENT RECEIVED FROM MR. CHASE OF THE EVENTS IS AS FOLLOWS: AFTER RETURNING FROM A TRIP TO ANOTHER AIRPORT, HE ENTERED THE PATTERN AT LIVERMOREAT A RT BASE FOR LANDING. THE PATTERN WAS VERY BUSY AND HE DID NOT CHECK FOR A GREEN LIGHT INDICATING THAT THE GEAR WAS FULLY EXTENDED. HE ONLY REMEMBERS PUTTING THE GEAR HANDLE IN THE DOWN POSITION. AFTER THE LANDING, WHICH WAS WITH THE GEAR UP, HE NOTICED THAT THE GEAR HANDLE WAS INDEED IN THE CORRECT DOWN POSITION BUT THE GEAR CIRCUIT BREAKER HAD POPPED NOT ALLOWING THE GEAR TO EXTEND. IN SPEAKING WITH THE GROUND CREW WHO REMOVED THE ACFT FROM THE RUNWAY MR. CHASE'S STROY OF THE POPPED CIRCUIT BREAKER WAS CONFIRMED.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.