ERA13IA192 · Embraer EMB-500
Progressive Aviation Embraer EMB-500 · Incident: system/component malfunction/failure (non-power) during landing
From Destin Executive Airport (DTS) to Key Field / Meridian Regional Airport (MEI)
Event
- NTSB case
- ERA13IA192
- 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
- Incident
- 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
Embraer EMB-500
- Aircraft type
- Embraer 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
- N196EC
- Operator
- Progressive Aviation
- Onboard fatalities
- Unknown
- Route
- From Destin Executive Airport (DTS), Destin, FLTo Key Field / Meridian Regional Airport (MEI), Meridian, MS
- 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 · 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
- None
Cause areas
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The pilot reported that the approach was uneventful and that he noted no anomalies during the flight. However, after touchdown and immediately upon brake application, the airplane began sliding in a manner that the pilot said was similar to hydroplaning even though, at the time of the incident, the runway was dry. Postincident examination revealed that both main landing gear tires were deflated and had wear marks that were associated with the wheels being locked while the airplane was in motion. Examination of the recordable data revealed that just before touchdown the "ANTI-SKID FAIL" message was displayed on the crew alerting system, and the associated maintenance message, "BRAKE CONTROL UNIT FAIL," was recorded on the central maintenance computer. Examination and testing of the brake control unit (BCU) fault log revealed that the loss of the antiskid function was caused by a disagreement between two BCU internal components of the wheel speed reading of each wheel. Although the airplane was equipped with numerous brake system protections, after the loss of wheel speed data, the system's protections against skidding were no longer operational, and a wheel lock on both main landing gear occurred. The investigation could not identify the cause of the disagreement of the wheel speed reading.
Probable cause
The failure of the main landing gear brake system’s antiskid system, which resulted in locked wheels during landing.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA13IA192
- Event ID
- 20130406X70217
- Case number
- ERA13IA192
- 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, damage. 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: 947dedc6ec82b7b839334ac31faa0bcf604d87fca222b1360355e7b9055e4eb2; retrieved 2026-09-15T21:14:17.853Z.