ERA24LA056 · Raytheon Aircraft Company 400A
Executive Air Services Raytheon Aircraft Company 400A · Accident: system/component malfunction/failure (non-power) during landing
From Teterboro Airport (TEB) to an unrecorded destination
Event
- NTSB case
- ERA24LA056
- 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
Raytheon Aircraft Company 400A
- Aircraft type
- Raytheon 400
- 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
- N800SD
- Operator
- Executive Air Services
- Onboard fatalities
- Unknown
- Route
- From Teterboro Airport (TEB), Teterboro, NJTo not recorded
- Aircraft age
- About 23 years (built 2000)
- 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 · landing roll
- 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
- System/component malfunction/failure (non-power)
- 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 › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
After a normal landing, the left main landing gear collapsed during the landing roll, which resulted in the airplane impacting the runway on its left belly and dragging the left wing about 3,800 ft down the paved surface of the runway before coming to rest. The left wing sustained substantial damage. Postaccident operational testing of the airplane’s landing gear system revealed that the left main landing gear down lock actuator did not provide adequate pressure to lock the landing gear, which allowed the landing gear to retract upon landing. Visual examination of the actuator did not reveal any anomalies, and it was not leaking fluid. No additional examination of the left landing gear actuator was performed.
Probable cause
The collapse of the airplane’s left main landing gear during the landing roll for undetermined reasons.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA24LA056
- Event ID
- 20231205193478
- Case number
- ERA24LA056
- 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, cause areas. 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: 685b2cab9e038b3921b61434fb717859be0b5dde266a0e3ea0584965b15e4f79; retrieved 2026-09-16T18:20:54.822Z.