NYC07LA006 · Beech BE-200
Airtec Beech BE-200 · Accident: airframe, component or system failure during landing
From St. Mary's County Regional Airport (2W6) to St. Mary's County Regional Airport (2W6)
Event
- NTSB case
- NYC07LA006
- 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
- N528WG
- Operator
- Airtec
- Onboard fatalities
- Unknown
- Route
- From St. Mary's County Regional Airport (2W6), Leonardtown, MDTo St. Mary's County Regional Airport (2W6), Leonardtown, MD
- 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
- Landing
- 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
- 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 manuals, procedure information › Inadequate
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
With all cockpit indications showing the landing gear was down and locked, the airplane touched down on the runway. Immediately after touchdown, the pilots heard the landing gear warning horn sound intermittently for several seconds, and then the right main landing gear collapsed. The airplane veered to the right, exited the runway, and came to rest. A postcrash fire ensued, and the crew exited without injury. A postaccident examination of the airplane revealed that the collapsed right main landing gear had penetrated the right main fuel tank and the majority of the right side of the fuselage had been consumed by fire. Examination of the left and right main landing gear assemblies revealed, that both downlock plates had been installed backwards, providing only a fraction of the design contact area between the plate and throat of the downlock hook. Examination of the manufacturer's component maintenance manual, which was used for the assembly and installation of the left and right main landing gear, revealed no guidance regarding downlock plate orientation during installation.
Probable cause
The airplane manufacturer's inadequate landing gear downlock plate maintenance orientation information, and the disengaged main landing gear.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC07LA006
- Event ID
- 20061027X01569
- Case number
- NYC07LA006
- 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: e2a6f0324f033f802800cced9ec738e5cfb2c693e6c5fbe603c1373b49800ece; retrieved 2026-09-22T04:19:32.287Z.