FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC06FA138 · Dornier DO-328-300

3 Jun 2006 · Manassas, VA, United States

East Coast Flight Services Dornier DO-328-300 · Accident: overrun during takeoff

From Washington Manassas Harry P. Davis Field (HEF) to Myrtle Beach International Airport (MYR)

Report a problem

Event

NTSB case
NYC06FA138
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

Dornier DO-328-300

Aircraft type
Dornier DO-328
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
N328PD
Onboard fatalities
Unknown
Route
From Washington Manassas Harry P. Davis Field (HEF), Manassas, VATo Myrtle Beach International Airport (MYR), Myrtle Beach, SC
Aircraft age
Not recorded
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
First occurrenceThe 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
Overrun
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

  • Flight/nav instruments, airspeed indicator › Blocked(partial)

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

Prior to departure on the maintenance repositioning flight, the captain discussed with the first officer an uneven fuel balance that they could "fix" once airborne, and a 25,000 feet msl restriction because of an inoperative air conditioning/pressurization pack. The captain also commented about the right pack "misbehaving", and a bleed valve failure warning. The captain also commented about aborting below 80 knots for everything, except for the bleed shutoff valve. During the takeoff roll, a single chime was heard, and the first officer reported a bleed valve fail message. The captain responded, "ignore it." Another chime was heard, and the first officer reported "lateral mode fail, pusher fail." The captain asked about airspeed and was advised of an "indicated airspeed miscompare." The captain initiated the aborted takeoff approximately 13 seconds after the second chime was heard. The crew was unable to stop the airplane, and it went off the end of the runway, and impacted obstructions and terrain. According to the flight data recorder, peak groundspeed was 152 knots and the time the aborted takeoff was initiated, and indicated airspeed was 78.5 knots. The captain and the airplane owner's director of maintenance were aware of several mechanical discrepancies prior to the flight, and the captain had advised the first officer that the flight was for "routine maintenance," but that the airplane was airworthy. Prior to the flight the first officer found "reddish clay" in one of the pitot tubes and removed it. A mechanic and the captain examined the pitot tube, and determined the tube was not obstructed. The captain's pitot tube was later found to be partially blocked with an insect nest. A postaccident examination of the airplane and aircraft maintenance log revealed that no discrepancies were entered in the log, and no placards or "inoperative" decals were affixed in the cockpit.

Probable cause

The partially blocked pitot system, which resulted in an inaccurate airspeed indicator display, and an overrun during an aborted takeoff. A factor associated with the accident was the pilot-in-command's delayed decision to abort the takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC06FA138
Event ID
20060618X00757
Case number
NYC06FA138
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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, coordinates. 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: 6e83f653832684458d40005c79204b35ccb48e00a1165f6844d4798be043acd6; retrieved 2026-09-21T18:45:26.142Z.