Plane Crash List

Cessna 310Q N69945

28 September 1999 · Salisbury, Maryland, United States · Serious injuries

Summary

On 28 September 1999 at about 10:50 local time, a Cessna 310Q registered N69945 was involved in an accident near Salisbury, Maryland, United States. 4 people were on board and 4 were seriously injured. The aircraft was substantially damaged. The NTSB has published a probable cause for this accident; it is quoted in full below.

The record

Date
at 10:50
Classification
Accident
Location
Salisbury, Maryland, United States
Nearest airport
Salisbury/Wicomico Region (SBY)
Coordinates
38.3700, -75.5794
Aircraft
Cessna 310Q
Registration
N69945
Category
Airplane
Engines
2
Operator
Not recorded
Operating rule
Part 135: Air Taxi & Commuter
Purpose of flight
Unknown
Phase of flight
Not recorded
Route
Unknown → Wilkes-Barre
Aircraft damage
Substantial
Weather
VMC
Light
Dawn
NTSB number
IAD99FA070

People

4 people were seriously injured.

On board Died Serious Minor Uninjured
4 0 4 0 0

Probable cause

The improper installation of the #2 cylinder that resulted in a fractured crankshaft and a total loss of engine power. Factors in the accident were the premature deployment of the landing gear and flaps by the pilot.

Quoted verbatim from the NTSB record. This site does not paraphrase or interpret it.

Read the full NTSB narrative

After takeoff, the right engine 'started surging' and the pilot turned back toward the departure airport. He configured the airplane for landing, and then attempted to secure the right engine. The engine seized, and the propeller stopped. The airplane was unable to maintain altitude sufficient to clear trees at the approach end of the landing runway, and the pilot performed a forced landing to a field approximately 1 mile short of the airport. The #2 cylinder of the right engine was replaced 160 aircraft hours prior to the accident. Examination of the right engine revealed the crankshaft was broken between the #2 main bearing journal and the #3 connecting rod journal. The mating surfaces of both crankcase halves, in the area of the #2 and #3 main bearing saddles, displayed fretting across the entire face surface. Examination of the fracture surfaces revealed that the damage was consistent with bearing shifting and rubbing. A warning published in the manufacturer's cylinder installation instructions stated: 'Failure to torque through bolt nuts on both sides of the engine can result in a loss of main bearing crush, main bearing shift and engine failure.' According to the FAA Airplane Flying Handbook, Engine Inoperative Approach And Landing: '...neither full flaps nor the landing gear should be extended until the landing is assured.'

Quoted verbatim from the NTSB record.

Other Cessna 310 accidents

Date Aircraft Location Operator Outcome Died
25 Jan 1999 Cessna 310N
N5080Q
Clearwater, Florida, United States
no coordinates
- No injuries -
23 Oct 1999 Cessna 310R
N7571Q
Columbus, Georgia, United States Maxwell Gunter AF Aero Club No injuries -
10 Nov 1999 Cessna 310Q
N310GC
Jacksonville, Florida, United States - No injuries -
3 Apr 1999 Cessna 310N
N4159Q
Cecilia, Kentucky, United States - Fatal 2
31 Jul 1999 Cessna 310N
N310DE
Eden Prairie, Minnesota, United States Bahram Akradi No injuries -
10 Feb 1999 Cessna 310R
N87464
Monticello, New York, United States Primac Courier Inc No injuries -

All 1,745 records for this type

Other accidents in this area

Date Aircraft Location Operator Outcome Died
5 Dec 1999 Cessna TR 182
N5260S
Clarksville, Maryland, United States - Minor injuries -
1 Aug 1999 Piper J3C-65
N70894
Frederick, Maryland, United States - No injuries -
16 May 1999 Cessna 182K
N2506Q
Baltimore, Maryland, United States - No injuries -
19 Sep 1999 Boeing Stearman PT17
N29743
Westminister, Maryland, United States - No injuries -
31 Mar 1999 Cessna 150
N8524J
Leonardtown, Maryland, United States Piedmont Flight Center No injuries -
21 Jun 1999 Cessna 182Q
N937FB
Rising Sun, Maryland, United States - Serious injuries -

All 170,864 records in United States