CEN22LA126 · Embraer Executive Aircraft Inc EMB-500
Eclipse Transport Embraer Executive Aircraft Inc EMB-500 · Accident: runway excursion during landing
From Burlington Alamance Regional Airport (KBUY) to Coleman A. Young Municipal Airport (KDET)
Event
- NTSB case
- CEN22LA126
- 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
- Event fatalities
- Unknown
- 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
Embraer Executive Aircraft Inc EMB-500
- Aircraft type
- Embraer Executive EMB-500
- 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
- N68NH
- Operator
- Eclipse Transport
- Onboard fatalities
- Unknown
- Route
- From Burlington Alamance Regional Airport (KBUY), Burlington, NCTo Coleman A. Young Municipal Airport (KDET), Detroit, MI
- Aircraft age
- About 8 years (built 2014)
- 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
- Runway excursion
- 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
- Environmental issues › Operating environment
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that after touchdown, he was unable to stop the airplane on the 5,092 ft runway due to snow and ice contamination. The airplane subsequently departed the end of the runway and impacted airport lighting equipment, which resulted in substantial damage to the right wing. The pilot stated that braking action was reported as 3/1/3, which corresponded to medium braking action for the initial 1/3 of the runway, poor braking action for the middle 1/3 of the runway, and medium braking action for the last 1/3 of the runway. The pilot reported no mechanical malfunctions or anomalies that would have precluded normal operation and that he should have diverted to another airport with better runway conditions.
Probable cause
The pilot’s decision to land on the contaminated runway with previous reports of unfavorable braking action.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN22LA126
- Event ID
- 20220222104672
- Case number
- CEN22LA126
- 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: f27b20ecee6debf145bd758adcff17a5502dedc7e3944143087b2a5660463a3c; retrieved 2026-09-16T14:58:43.859Z.