The U.S. aircraft register, updated daily
Accidents · NTSB CEN10IA535 · Final report

Embraer 500 incident near Brenham, Texas, September 10, 2010

On September 10, 2010 at about 5:52 pm local time, a Embraer 500, registered N226CP, suffered minor damage in an incident during prior to flight near Brenham, Texas (Brenham Municipal Airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilots’ decision to depart with a known failed brake control unit.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
September 10, 2010 · about 5:52 pm local time · cases in 2010
Place
Brenham, Texas · Brenham Municipal Airport · cases near this airport · map
Type
Incident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Embraer 500 Phenom 100
Registration
N226CP · registry record · serial 50000071
Damage
Minor damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

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.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Sys/Comp malf/fail (non-power) during prior to flight defining event
  2. Sys/Comp malf/fail (non-power) during takeoff
  3. Sys/Comp malf/fail (non-power) during landing
  4. Loss of control on ground during landing (landing roll)
  5. Runway excursion during landing (landing roll)
  6. Landing gear collapse during landing (landing roll)

The NTSB's findings

  • cause Personnel issues › Action/decision › Info processing/decision › Decision making/judgment › Flight crew
  • Aircraft › Aircraft systems › Landing gear system › Landing gear brakes system › Failure other cases naming the landing gear

Pilot

  • Certificate: airline transport pilot
  • Ratings: multi-engine land; single-engine land; instrument: airplane
  • Flight time: 1,627 hours in all; 54 in this make and model; 44 in the last 90 days; 16 in the last 30 days; 1,408 as pilot in command; 0 on instruments
  • Last flight review: October 30, 2009
  • Medical certificate: Class 3 (without waivers/limitations)
  • Seat: left
  • Injury: no injuries

Co-pilot

  • Certificate: commercial pilot
  • Ratings: multi-engine land; single-engine land; single-engine sea; instrument: airplane; rotorcraft: helicopter
  • Flight time: 7,026 hours in all; 40 in this make and model; 20 in the last 90 days; 13 in the last 30 days; 3,206 as pilot in command; 0 on instruments
  • Last flight review: October 30, 2009
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: rgt
  • Injury: no injuries

The aircraft

  • Airframe total time: 37 hours
  • Last inspection: annual inspection
  • Maximum gross weight: 10,472 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine 1: Pwc PW617F-E (turbofan); 0 hours total
  • Engine 2: Pwc PW617F-E (turbofan); 0 hours total

The flight

  • Departed from: TUS Tucson AZ at 3:30 pm
  • Destination: 11R Brenham TX
  • Flight plan: IFR
  • Runway 16, 6,003 ft by 75 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 220° at 9 knots
  • Visibility: 10 statute miles
  • Temperature: 90°F (32°C), dew point 72°F (22°C)
  • Altimeter: 29.89 inHg
  • Observation at 5:45 pm from 11R

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

21 documents, released by the NTSB on December 12, 2012. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.

#DocumentWhat it is
1 Summary of On-site and Follow-up Examinations by the NTSB Investigator in Charge PDF, 6 pages View Download
2 Pilot/operator Aircraft Accident Report, NTSB Form 6120.1 PDF, 10 pages View Download
3 Crewmember Telephone Interview on September 10, 2010 PDF, 1 page View Download
4 Crewmember Telephone Interviews on October 7 and 12, 2010 PDF, 3 pages View Download
5 Flight Data Recorder 10 - Specialist's Factual Report PDF, 11 pages View Download
6 Flight Data Recorder 10 - Attachment 1 - Tabular Data - Flight - (Csv Format) zip file Download
7 Cockpit Voice Recorder 12 - Specialist's Factual Report PDF, 5 pages View Download
8 Witness Statements PDF, 2 pages View Download
9 Quick Reference Handbook (QRH) - Selected Pages Showing Procedures for Anti-skid Fail and Brk Fail and Selected Pages Showing Landing Performance and Landing Distance Correction for Abnormal Landing PDF, 6 pages View Download
10 MEL Guidance for Cas Messages PDF, 1 page View Download
11 Embraer Phenom - Flight Operations Support Letter, Dated November 11, 2009 PDF, 1 page View Download
12 FAA Safety Alert for Operators Safo 06102 - Subject: Landing Performance Assessments at Time of Arrival (Turbojets) PDF, 11 pages View Download
13 Map PDF, 1 page View Download
14 Photo 1 - Showing Location of Initial Skid Marks on the Runway PDF, 1 page View Download
15 Photo 2 - Showing Uneven Skid Marks on the Runway Surface PDF, 1 page View Download
16 Photo 3 - Disabled Airplane in the Grass on the Side of the Runway PDF, 1 page View Download
17 Photo 4 - Damage to the Left Main Landing Gear Tire PDF, 1 page View Download
18 Photo 5 - Damage to the Right Main Landing Gear and Tire PDF, 1 page View Download
19 Photo 6 - Damage to the Partially Collapsed Right Main Landing Gear. PDF, 1 page View Download
20 Statement of Party Representatives to NTSB Investigation PDF, 2 pages View Download
21 Release of Aircraft Wreckage, NTSB Form 6120.15 PDF, 2 pages View Download

The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN10IA535.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.