FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC82FNA13 · Beech E33

11 May 1982 · Bedford, MA, United States

Beech E33 · Accident: on ground/water collision with object while taxiing

From Bedford, MA to Bedford, MA

Report a problem

Narrative check · The NTSB narrative appears to contradict this record's aircraft involved. Values are shown as recorded, not corrected; compare with the narrative.

Event

NTSB case
NYC82FNA13
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
0
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 E33 Possible conflict

Aircraft type
Beechcraft 33
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
N7457N
Onboard fatalities
Unknown
Route
From Bedford, MATo 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
Taxi
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
On ground/water collision with object
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

  • Pilot in command › Aircraft preflight, inadequate
  • Pilot in command › Proper assistance, not obtained

Approximate · Estimated position: the centre of Bedford, MA, the place the record names. Not the accident site.

NTSB narrative

THE PILOT WAS UNABLE TO START THE AIRCRAFT WITH THE ELECTRIC STARTER WHEN THE BATTERY HAD INSUFFICIENT POWER TO CRANK THE ENGINE. THE PILOT STATED THAT HE SHUT OFF THE BATTERY AND ALTERNATOR SWITCHES, TURNED OFF THE MAGNETO SWITCH, AND REMOVED THE KEYS. HE STATED THAT HE THEN EXITED THE AIRCRAFT AND BEGAN PULLING THE ENGINE THROUGH TO COAT THE CYLINDER WALLS WITH OIL. SUBSEQUENTLY, THE ENGINE STARTED AND THE AIRCRAFT TRAVELED ACROSS THE RAMP AND STRUCK ANOTHER PLANE. AN INVESTIGATION REVEALED THAT THE KEYS COULD BE REMOVED WITH THE IGNITION SWITCH IN THE RIGHT MAG POSITION. A TEARDOWN OF THE SWITCH REVEALED THAT THE CONTACTS WERE BURNED AND THE LOCK CYLINDER CHAMBER WAS WORN. THERE WAS NO RECORD SHOWING COMPLIANCE WITH AD 76-07-12 FOR AN INSPECTION OF THE BENDIX IGNITION SWITCH, PN 10-357200-1.

Verbatim NTSB analysis from the NTSB dataset

Sources

NTSB record NYC82FNA13
Event ID
20020917X04052
Case number
NYC82FNA13
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. 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: 5678dd29fcd1b1274c8d6251f3ebeb363891b3ac4d15534078c02177c8c6e68c; retrieved 2026-09-24T03:15:58.525Z.