FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

MIA05LA143 · Cirrus Design Corp. SR22

4 Aug 2005 · Orlando, FL, United States

Cirrus Design Corp. SR22 · Accident: airframe, component or system failure during takeoff

From Orlando Executive Airport (KORL) to Peter O Knight Airport (KTPF)

Report a problem

Event

NTSB case
MIA05LA143
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
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

Cirrus Design Corp. SR22

Aircraft type
Cirrus SR22
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
N513CD
Operator
Garrett L. Ermish · private individual
Onboard fatalities
Unknown
Route
From Orlando Executive Airport (KORL), Orlando, FLTo Peter O Knight Airport (KTPF), Tampa, FL
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
Takeoff · rejected takeoff
First occurrenceThe 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
Airframe, component or system failure
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

  • Fluid, hydraulic › Leak
  • Landing gear, normal brake system › Overtemperature
  • Manufacturer › Acft/equip, inadequate design

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

The commercial certificated pilot was departing on an IFR cross-country personal flight under Title 14, CFR Part 91. During the takeoff roll, he noted an intermittent loss of airspeed indication, and aborted the takeoff. After exiting the runway, he stopped the airplane on a taxiway, shut off the engine, and exited to check the pitot/static tube. He smelled an odor, and saw white smoke coming from the right main landing gear tire wheel pant. He heard a "poof", and saw flames engulf the right wheel. Postaccident examination of the right brake assembly revealed that the right brake caliper was heat damaged, cracked and deformed. The O-rings around the caliper pistons were thermally damaged. The airplane's nose wheel casters freely, and ground steering is accomplished by differential braking of the main landing gear wheels. The airplane's Pilot's Operating handbook (POH) cautions pilots that when taxiing, they should use minimum power, and notes that excessive braking may result in overheated or damaged brakes. Two months before the accident, the manufacturer issued an Owner Service Advisory (OSA), which advised pilots to not ride the brakes, which could produce excessive heat, premature brake wear, and the increased possibility of brake failure. The airplane's maintenance records contained several entries about the brake system. Eight months before the accident, the left brake pads were replaced, and the brake reservoir needed servicing. Two weeks later, the right brake was reported as leaking, and the maintenance discrepancy noted, in part: "Removed brake calipers, found O-rings on pistons to be excessively heated due to excessive brake usage, causing piston to blow out. Found linings with cracks and chips missing." Two months before the wheel fire, all the brake linings were again replaced. Following the accident, the manufacturer issued Service Bulletin SB2X-32-13, on December 15, 2005, which called for the installation of improved brake assemblies. On January 18, 2006, the manufacturer issued Mandatory Service Bulletin, SB2X-32-14, that added temperature indicators on the brake assemblies, modified the wheel pant assemblies to provide access to the temperature indicators, and revised the airplane's POH. On February 9, 2006, the FAA issued a Special Airworthiness Information Bulletin (SAIB), CE-06-30, which recommended compliance with the manufacturer's service bulletins.

Probable cause

The manufacturer's defective wheel brake assembly design and a leaking wheel brake, resulting in an overheated brake assembly and a wheel fire during an aborted takeoff.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record MIA05LA143
Event ID
20050823X01300
Case number
MIA05LA143
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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: 926839be28d99169e17a87bda962b7b5671b44e9226bf6a2b96b65cc493ac156; retrieved 2026-09-22T05:32:54.590Z.