NYC05LA009 · Beech BE-200
Twin County Aviation Beech BE-200 · Accident: in flight collision with object on approach
From Piedmont Triad International Airport (GSO) to Eastern WV Regional Airport/Shepherd Field (MRB)
Event
- NTSB case
- NYC05LA009
- 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 BE-200
- Aircraft type
- Beechcraft BE-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
- N888TR
- Operator
- Twin County Aviation
- Onboard fatalities
- Unknown
- Route
- From Piedmont Triad International Airport (GSO), Greensboro, NCTo Eastern WV Regional Airport/Shepherd Field (MRB), Martinsburg, WV
- 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 missed 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
- 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 › In-flight planning/decision, improper
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The pilot approached the destination airport and entered a holding pattern to wait for the weather to improve. After about 20 minutes, the weather seemed to improve, and because the pilot could occasionally see the ground, he decided to conduct an instrument approach. About 50 feet above decision height, the pilot had the runway environment in sight, and estimated the in-flight visibility was about 1/2 mile. During the landing, the pilot lost all forward visibility and executed a missed approach, but before a positive rate of climb could be established, the airplane touched down left of the runway on grass, and the left main landing gear struck a taxiway sign. About 10 feet past the sign, the airplane became airborne, and the pilot continued the missed approach. The pilot then diverted to an alternate airport, and during the landing the left main landing gear collapsed, resulting in substantial damage. The automated surface observation system and a witness both reported that the weather at the time of the accident was below the minimums prescribed in the instrument approach procedure.
Probable cause
The pilot's improper in-flight decision to continue the instrument approach and landing, which resulted in a collision with a sign. A factor was the below instrument approach landing minimum weather conditions.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC05LA009
- Event ID
- 20041129X01871
- Case number
- NYC05LA009
- 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, coordinates. 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: e6f706207a17b1dbb828158c30f1135c773e4001316e3caeaf1b98932032a398; retrieved 2026-09-22T06:34:24.125Z.