CEN10IA535 · Embraer 500 Phenom 100
Embraer 500 Phenom 100 · Incident: system/component malfunction/failure (non-power) before flight
From Tucson International Airport (TUS) to Brenham Municipal Airport (11R)
Event
- NTSB case
- CEN10IA535
- 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 500 Phenom 100
- Aircraft type
- Embraer 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
- N226CP
- Operator
- Unknown
- Onboard fatalities
- Unknown
- Route
- From Tucson International Airport (TUS), Tucson, AZTo Brenham Municipal Airport (11R), Brenham, TX
- 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
- Prior to flight
- 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
- Minor
Cause areas
- Personnel issues › Action/decision
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The crewmembers reported that they were still on the ground and noticed a crew alerting system (CAS) message indicating a brake failure. They decided to continue their departure, and the CAS message stayed active for the entire flight. After touchdown, the co-pilot was flying the airplane when he discovered that the brakes did not work, and the airplane began skidding when he pulled the emergency parking brake handle. The airplane was moving about 50 to 60 knots when both tires blew. While the airplane was still skidding on the runway, the nose rotated about 120 degrees to the left and the airplane exited the left side of the runway while moving sideways to the right. The right main landing gear collapsed after contacting the soft ground on the side of the runway. A postaccident examination of the brake control unit (BCU) revealed a fault on the printed circuit board that led to an open circuit for a component installed on the board. The open circuit caused the failure of the BCU and the loss of normal braking. An examination of the remaining systems revealed no anomalies.
Probable cause
The pilots’ decision to depart with a known failed brake control unit.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record CEN10IA535
- Event ID
- 20100912X91459
- Case number
- CEN10IA535
- 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, 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: b524df7e6d7aabb6b63edc58af937ed30df04c5a9e33d8e8189361de8dd164a5; retrieved 2026-09-15T15:10:15.864Z.