NYC83FA126 · Beech B36TC
Beech B36TC · Accident: in flight collision with object on approach
From Grand Strand Airport (CRE) to Republic Airport (FRG)
Event
- NTSB case
- NYC83FA126
- 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
- 4 · 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
- Instrument Meteorological Cond
Beech B36TC
- Aircraft type
- Beechcraft 36
- 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
- N837E
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Grand Strand Airport (CRE), Myrtle Beach, SCTo Republic Airport (FRG), Farmingdale, NY
- 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 · IFR final approach
- 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
- In flight collision with object
- 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
- Wire, static
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Pilot in command › Decision height, not maintained
- Pilot in command › IFR procedure, improper
- Pilot in command › Missed approach, not performed
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
THE ACFT COLLIDED WITH A POWERLINE STATIC WIRE DURING AN INSTRUMENT LANDING APPROACH. THE PRIVATE PLT WAS INSTRUMENT RATED AND HAD RECEIVED A WEATHER BRIEFING AND FILED AN IFR FLT PLAN. HE COMMENTED TO THE BRIEFER THAT 'IT DOESN'T SOUND TOO GOOD' AND THAT HE WOULD CALL AGAIN IN AN HOUR OR SO. ABOUT AN HOUR AND ONE HALF LATER HE AIR FILED AN IFR FLT PLAN. WHEN HE REACHED HIS DESTINATION HE WAS CLEARED FOR THE ILS APPROACH AND WAS CLEARED TO LAND WHEN HE REPORTED THE OUTER MARKER. THERE WERE NO FURTHER TRANSMISSIONS RECEIVED FROM THE PLT. RADAR SHOWED THE ACFT ON CENTERLINE AND DECENDING TO 400 FT ABOUT 1 MILE FROM THE END OF THE RWY. WITNESSES SAW THE ACFT AT LOW ALT AND SAW IT COLLIDE WITH THE POWERLINE. ONE SAW A BLUE ARC AFTER THE COLLISION. 3 REPORTED AN EXPLOSIVE SOUND AND BLACK SMOKE FOLLOWING THE COLLISION. THE VISIBILITY WAS DESCRIBED AS ONE TO TWO MILES. THE WIRE THAT WAS HIT WAS 78 FT AGL (149 FT MSL). DECISION HEIGHT FOR THE LANDING IS 329 FT AND VISIBILITY ONE MILE. THE ILS SYSTEM HAD BEEN USED SUCCESSFULLY JUST PRIOR TO THE ACCIDENT.
Verbatim NTSB analysis from the NTSB dataset
Sources
NTSB record NYC83FA126
- Event ID
- 20001214X43115
- Case number
- NYC83FA126
- 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: 15dc2fe5af46976b03cebe5b25967070802b5674df49f73eb3c3c22aae28b8d1; retrieved 2026-09-21T06:43:58.145Z.