NYC88LA019 · Beech 19A
Beech 19A · Accident: airframe, component or system failure en route
From Millville Municipal Airport (MIV) to Flying W Airport (N14)
Event
- NTSB case
- NYC88LA019
- 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 19A
- Aircraft type
- Beechcraft 19
- 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
- N5082T
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Millville Municipal Airport (MIV), Millville, NJTo Flying W Airport (N14), Lumberton, NJ
- 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
- En route · climb to cruise
- 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
- Airframe, component or system failure
- Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
- Pole
- 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
- Electrical system, circuit breaker › Popped/tripped
Approximate · Estimated position: the centre of Buena, NJ, the place the record names. Not the accident site.
NTSB narrative
The Beech model 19 took off in instrument meteorological conditions (IMC) with the owner/operator and a flight instructor onboard. A few minutes after takeoff the aircraft experienced a loss of electrical power. The alternator circuit breaker popped, the flight instructor reset it and it popped again. It was not reset. Because of the IMC and the rapid loss of electrical power, a precautionary off airport landing on a road was made. The aircraft received substantial damage upon striking a pole. The battery was found with a specific gravity of zero; the alternator worked when ground checked; and the alternator circuit breaker was found in the open position. The reason that the alternator circuit breaker tripped was not determined.
This report was modified on February 9, 2005.
Probable cause
a loss of electrical power for undetermined reasons, which necessitated a precautionary landing. Factors were rain, clouds, dark night, and the pole.
This report was modified on February 9, 2005.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC88LA019
- Event ID
- 20001213X32434
- Case number
- NYC88LA019
- 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: e0e16d0430593a5a2f09fe31406c47188a3bd1d7764efd09eef44137ef23162f; retrieved 2026-09-22T00:41:54.343Z.