Freight Runners Beech 99 A accident
Beech 99 A · Accident: landing gear collapse while taxiing
From Manchester-Boston Regional Airport (MHT) to an unrecorded destination
Event
- NTSB case
- ERA21LA021
- 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
- Charter & commuter
- 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 99 A
- Aircraft type
- Beechcraft 99
- 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
- N499CZ
- Operator
- Freight Runners
- Onboard fatalities
- Unknown
- Route
- From Manchester-Boston Regional Airport (MHT), Manchester, NHTo not recorded
- Aircraft age
- About 51 years (built 1969)
- 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 135: Air Taxi & Commuter
- 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 · from runway
- Defining eventThe 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
- Landing gear collapse
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
While taxiing to the ramp, the airplane’s right main landing gear collapsed, resulting in substantial damage to the right wing. Examination of the right main landing gear drag leg support fitting and angle bracket revealed several areas of fatigue cracking with multiple origins. The attach angle bracket fracture exhibited features consistent with fatigue. The reason for the crack initiation could not be determined. A review of the maintenance procedures performed on the right main landing gear 8 days prior to the accident found that they instructed the mechanic to add grease to the drag leg fitting. The procedures did not specify to examine the landing gear for fatigue cracking or anomalies; therefore, it is unlikely that the mechanic would have looked in the area of the cracked main landing gear drag leg support fitting and angle bracket. Furthermore, there was no nondestructive testing procedures for examining the main landing gear drag brace, so it’s unlikely an inspection would have detected the multiple areas of fatigue cracking.
Probable cause
A failure of the right main landing gear drag leg support fitting and angle bracket as a result of multiple areas of fatigue cracking.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA21LA021
- Event ID
- 20201015102152
- Case number
- ERA21LA021
- Dataset
- full-current
- Source SHA-256
- 5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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: 9c7116dbf1c2f41bf0f70f461f163df190e84cfc3491e1314d2fad2cf49340ca; retrieved 2026-09-16T13:14:47.327Z.