FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA13CA355 · Beech 58

31 Jul 2013 · New Bedford, MA, United States

Randolph Aviation Beech 58 · Accident: collision during takeoff/landing on approach

From Martha's Vineyard Airport (MVY) to New Bedford Regional Airport (EWB)

Report a problem

Event

NTSB case
ERA13CA355
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 58

Aircraft type
Beechcraft 58
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
N58DL
Onboard fatalities
Unknown
Route
From Martha's Vineyard Airport (MVY), Vineyard Haven, MATo New Bedford Regional Airport (EWB), New Bedford, MA
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
Approach · VFR pattern final
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
Collision during takeoff/landing
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

  • Aircraft › Aircraft oper/perf/capability
  • Personnel issues › Action/decision

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

NTSB narrative

According to the pilot, he was completing a short cross-country flight and planned a practice short field landing at the destination airport. He landed on his planned touchdown point, but did not take the height of the runway threshold lights into consideration. During the final approach, the airplane struck the approach lighting system at the 400 and 600-foot positions from the runway end. An inspector from the Federal Aviation Administration examined the airplane and confirmed substantial damage to the lower surface of the fuselage, including both wing bulkheads. The pilot reported no pre-impact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The runway had a 413-foot-long displaced threshold and the touchdown occurred near the front edge of the threshold.

Probable cause

The pilot's improper decision to land in the displaced threshold, resulting in a collision with the approach lighting system.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record ERA13CA355
Event ID
20130807X40746
Case number
ERA13CA355
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: 66641a9d4a6778c14a72a56932316de4308105228798e03859d56e87b6636be6; retrieved 2026-09-15T22:27:04.369Z.