FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

WPR18LA179 · Cessna 340A A

25 Jun 2018 · Orlando, FL, United States

Little Dreams Aviation Cessna 340A A · Accident: runway excursion during takeoff

From Orlando Executive Airport (ORL) to Smith Reynolds Airport (INT)

Report a problem

Event

NTSB case
WPR18LA179
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Completed
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
Unknown
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Cessna 340A A

Aircraft type
Cessna 340
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N60E
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (ORL), Orlando, FLTo Smith Reynolds Airport (INT), Winston Salem, NC
Aircraft age
About 39 years (built 1979)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Takeoff · rejected takeoff
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Runway excursion
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

  • Not determined › Not determined
  • Personnel issues › Action/decision

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB 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.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record WPR18LA179
Event ID
20180625X05502
Case number
WPR18LA179
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: ecdd04593eb50ebbaf0f125e0bf9d45b7939a569332640312062458da0fd7e88; retrieved 2026-09-16T07:39:04.679Z.