# Incident 20070627824809I: Cessna 310Q, Stevensville, MD, June 27, 2007

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 27, 2007, 23:30 local time
- Place: Stevensville, MD
- Airport: Bay Bridge
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.9765° N, 76.3300° W: Placed by OpenAirDocs at BAY BRIDGE (W29), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.9765&lon=-76.3300&mi=10
- Aircraft: N92ES, registered now (https://openairdocs.org/aircraft/N92ES) (OpenAirDocs)
- Registry model: Cessna 310Q (registry code 2074242, https://openairdocs.org/model/cessna-310q) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: CESSNA 310Q
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 875 total, 6 in this make and model, 6 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20070627824809I

## Narrative

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

(-23) ON 6/27/2007 AT 11:30 PM LOCAL, THE PILOT ^PRIVACY DATA OMITTED^ WAS ACTING AS PILOT IN COMMAND OF A CE-310Q WHEN HE FAILED TO LOWER THE LANDING GEAR DURING A LANDING ON RUNWAY 11 AT BAY BRIDGE AIRPORT, STEVENSVILLE, MD.

## Other reports on N92ES (2)

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

- [Incident 20100423040019I](https://openairdocs.org/incident/20100423040019I), Apr 23, 2010: Cessna 310Q (N92ES), Pittsburgh, PA, No damage. Pittsburgh int'l airport, PA: N92ES, a C310, experienced electrical and radio failure and the smell of smoke while enroute to the bay bridge airport, MD. The…
- [Incident 19790429025299I](https://openairdocs.org/incident/19790429025299I), Apr 29, 1979: Cessna 310Q (N92ES), Danville, IL, Minor damage. Nose gear not locked for landing,collapsed. Had been retracted with flat strut, causing linkage to seperate.

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.