FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC08LA323 · Beech A200

25 Sept 2008 · Bridgewater, VA, United States

Dynamic Aviation Group Beech A200 · Accident: runway excursion during landing

From Bridgewater Air Park (VBW) to Bridgewater Air Park (VBW)

Report a problem

Event

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

Beech A200

Aircraft type
Beechcraft 200
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
N30W
Onboard fatalities
Unknown
Route
From Bridgewater Air Park (VBW), Bridgewater, VATo Bridgewater Air Park (VBW), Bridgewater, VA
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
Landing
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

  • Environmental issues › Conditions/weather/phenomena
  • Environmental issues › Physical environment
  • Personnel issues › Action/decision

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

NTSB narrative

The pilot, an employee of the United States Department of Interior (DOI), was conducting a post-maintenance test flight of the airplane, which was on long term lease to the DOI. For the flight, despite the presence of drizzle, a tailwind, and obstacles, the pilot elected to use a down-sloping, non-grooved runway with a 41:1 approach slope and a displaced threshold, with an available landing length of 2,377 feet. The pilot executed a go-around after touchdown on his first landing attempt, stating that something did not feel right with the landing. The pilot then attempted another landing, touching down approximately 700 feet down the runway before applying reverse thrust and brakes. Because the runway was wet, the braking action was poor and he realized that he was probably going to overrun the end of the runway. However, he elected not to go around due to the airplane’s low indicated airspeed, the configuration of the airplane, the remaining runway, the rising terrain, and the presence of houses. The airplane then rolled off the pavement on to grass, where the braking effectiveness was further reduced, before rolling down a steep embankment and into a river. The airplane sustained substantial damage to its wing structure during the accident sequence. Postaccident examination of the airplane revealed no preimpact mechanical malfunctions or abnormalities.

Review of the DOI's National Business Center, Aviation Management Directorate's Operational Policy Memorandums (OPMs) did not reveal any guidance that pertained to test flights. Additionally, the "Aviation Management – Document Library Index"—which included the OPMs, information bulletins, handbooks, and reference guides—included no single operations manual containing all of the information for ready reference by the DOI's pilots, nor was a mandate discovered which would require them to have such information in their possession during flight operations.

Probable cause

The pilot's decision to land with a tailwind on a short, wet runway, resulting in landing long and runway overrun. Contributing to the accident was the operator’s lack of standard operating procedures for test flights.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC08LA323
Event ID
20081004X12024
Case number
NYC08LA323
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: 75b3cdf0dfe6a72aeca19be8cf239dda9cc745c7d4faf52f7445d05ccc74b5f8; retrieved 2026-09-15T10:22:38.983Z.