# Accident 20030330008229A: Cessna 310F, Reidsville, NC, March 30, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 30, 2003, 17:20 local time
- Place: Reidsville, NC
- Airport: Rockingham County Nc Shiloh
- Damage: Substantial damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 36.4369° N, 79.8508° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=36.4369&lon=-79.8508&mi=10
- Aircraft: N5810X, a cancelled registration (https://openairdocs.org/deregistered/N5810X-2006-05-04) (OpenAirDocs)
- Registry model: Cessna 310F (registry code 2074216, https://openairdocs.org/model/cessna-310f) (OpenAirDocs)
- Registry engine: Continental IO-470 series (registry code 17044, https://openairdocs.org/engine/continental-io-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 310F
- Reported engine: CONT IO470*
- Fatal injuries: 0
- Pilot flight hours: 17,420 total, 20 in the last 90 days
- NTSB investigation: [NTSB ATL03LA071](https://openairdocs.org/ntsb/ATL03LA071) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030330008229A

## Narrative

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

(-23) ON 3/30/03 AIRCRAFT N5810X A CESSNA 310F DEPARTED OCEAN SPRING, MISSISSIPPI AIRPORT (5R2) ENROUTE TO ROCKINHAM-SHILOH, NC AIRPORT (78N). THE AIRCRAFT DEPARTED OCEAN SPRING, MS AFTER UNDERGOING AN ANNUAL MAINTENANCE INSPECTION AND WAS RETURNING BACK TO IT'S HOME BASE AIRPORT. THE AIRLINE TRANSPORT RATED PILOT AND OWNER OF THE AIRCRAFT STATED THAT ON DEPARTURE FROM OCEAN SPRINGS AIRPORT HE SELECTED THE LANDING GEAR HANDLE TO THE STOWED POSITION AND HEARD A "POPPING NOISE", AFTER A CHECK OF THE COCKPIT INSTRUMENTS HE DETERMINED THAT ALL INDICATIONS WERE NORMAL, AND DECIDED TO CONTINUE ONTO ROCKINGHAM, NC AIRPORT. ON APPROACH INTO ROCKINGHAM COUNTY AIRPORT THE PILOT STATED THAT HE SELECTED THE LANDING GEAR DOWN FOR LANDING AND DID NOT GET A GEAR DOWN & LOCKED INDICATION, AND THAT HE CYCLED THE GEAR SWITCH THREE TIMES WITH SAME RESULTS. DURING A FLYOVER OF THE AIRPORT, THE FBO MANAGER INFORMED THE PILOT THAT THE NOSE LANDING GEAR HAD FAILED TO EXTEND. THE PILOT STATED THAT HE ELECTED TO LAND THE AIRCRAFT ON THE GRASS FIELD ALONG THE RUNWAY TO AVOID THE POSSIBILITY OF SPARKING AND FIRE. THE AIRCRAFT SUSTAINED SUBSTANTIAL DAMAGE, AND THE PILOT AND CO-PILOT RECEIVED MINOR INJURIES.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB ATL03LA071](https://openairdocs.org/ntsb/ATL03LA071), Mar 30, 2003: Cessna 310F (N5810X), Reidsville, NC, substantial damage. Probable cause: The failure of maintenance personnel to properly install the nose gear landing door link during an annual inspection that resulted in the failure of the nose gear to fully extend.

## Other reports on N5810X (1)

Matched to the same aircraft by N-number and date.

- [Incident 19830310012399I](https://openairdocs.org/incident/19830310012399I), Mar 10, 1983: Cessna 310F (N5810X), Albuquerque, NM, Minor damage. Took off with a flat nose gear strut. Jammed gear popped circuit breaker. Pilot failed to notice. Landed gear up.

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.