Runway excursion Accident Cessna 340A N60E,
ASN logo
ASN Wikibase Occurrence # 212626
 
This information is added by users of ASN. Neither ASN nor the Flight Safety Foundation are responsible for the completeness or correctness of this information. If you feel this information is incomplete or incorrect, you can submit corrected information.

Date:Monday 25 June 2018
Time:08:15
Type:Silhouette image of generic C340 model; specific model in this crash may look slightly different    
Cessna 340A
Owner/operator:Little Dreams Aviation LLC
Registration: N60E
MSN: 340A0663
Year of manufacture:1979
Total airframe hrs:4518 hours
Engine model:Continental TSIO-520 SER
Fatalities:Fatalities: 0 / Occupants: 4
Aircraft damage: Substantial
Category:Accident
Location:Executive Airport (KORL), Orlando, FL -   United States of America
Phase: Take off
Nature:Private
Departure airport:Orlando Executive Airport, FL (ORL/KORL)
Destination airport:Winston-Salem-Smith-Reynolds Airport, NC (INT/KINT)
Investigating agency: NTSB
Confidence Rating: Accident investigation report completed and information captured
Narrative:
The pilot reported that engine start, run-up, and taxi were all normal in preparation for the personal flight. The pilot began the takeoff roll using the full length of the dry, paved 6,000-ft runway, but shortly thereafter he felt a "sudden lag." The maximum speed he observed on the airspeed indicator was 43 knots, and the airspeed indicator needle "seemed to be fluttering." He confirmed that the engine controls were properly set and then decided to discontinue the takeoff about halfway down the runway by reducing power and applying the brakes and spoilers to decelerate the airplane. The airplane did not appear likely to stop before overrunning the end of the runway, so the pilot steered the airplane to the right as it ran off the runway end. The airplane impacted and stopped in a culvert about 500 ft beyond the runway and sustained substantial damage to the fuselage nose.
Postaccident examination of the airplane, airspeed indication system, and engines did not reveal any preimpact mechanical malfunctions or failures that would have precluded normal operation. Several months after the accident, the airplane was repaired, and engine test runs revealed two minor but unrelated turbocharger problems. One problem affected the left engine, and the other affected the right engine, but they did not manifest themselves concurrently. In each case, the affected engine did not develop full rpm, but the other engine did develop full rpm. The investigation was unable to determine whether these problems existed at the time of the accident takeoff. If they did exist, unless they occurred simultaneously, they would have manifested as a significant asymmetric thrust between the two engines, which would have been obvious to the pilot. The pilot did not report any shortcomings in engine rpm or such thrust asymmetry. The airplane was subsequently ferried to its destination, and both engines operated normally for that flight.
Accident site review revealed that the airplane traversed a total distance of about 6,500 ft during its takeoff roll and stop. Calculations performed postaccident indicate that, with a normal acceleration to 43 knots, had the airplane continued at that speed, it would have taken 35 seconds to reach the halfway point of the runway, at which point the pilot would have had 3,000 ft remaining to stop from 43 knots, which should have been sufficient.
The investigation was unable to determine the reason for the airplane not accelerating above 43 knots. However, the pilot’s delay in aborting the takeoff when the airplane did not accelerate above 43 knots resulted in the runway overrun.

Probable Cause: The pilot's delayed decision to discontinue the takeoff when confronted with abnormal acceleration and airspeed indication; the reason for the abnormal acceleration could not be determined based on the available information.

Accident investigation:
cover
  
Investigating agency: NTSB
Report number: WPR18LA179
Status: Investigation completed
Duration: 1 year and 11 months
Download report: Final report

Sources:

NTSB
https://flightaware.com/live/flight/N60E

FAA register: http://registry.faa.gov/aircraftinquiry/NNum_Results.aspx?NNumbertxt=60E

Location

Revision history:

Date/timeContributorUpdates
25-Jun-2018 18:30 Geno Added
08-Jun-2020 08:38 ASN Update Bot Updated [Nature, Departure airport, Destination airport, Source, Narrative, Accident report, ]
08-Jun-2020 17:21 harro Updated [Departure airport, Destination airport, Source, Narrative, Accident report, ]

Corrections or additions? ... Edit this accident description

The Aviation Safety Network is an exclusive service provided by:
Quick Links:

CONNECT WITH US: FSF on social media FSF Facebook FSF Twitter FSF Youtube FSF LinkedIn FSF Instagram

©2024 Flight Safety Foundation

1920 Ballenger Av, 4th Fl.
Alexandria, Virginia 22314
www.FlightSafety.org