LAX08LA217 · Lancair Company LC41-550FG
Mccormick Enterprises Lancair Company LC41-550FG · Accident: system/component malfunction/failure (non-power) while taxiing
From Friedman Memorial Airport (SUN) to Boise Air Terminal/Gowen Field (BOI)
Event
- NTSB case
- LAX08LA217
- 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
Lancair Company LC41-550FG
- Aircraft type
- Lancair LC41
- 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
- N2544W
- Operator
- Mccormick Enterprises
- Onboard fatalities
- Unknown
- Route
- From Friedman Memorial Airport (SUN), Hailey, IDTo Boise Air Terminal/Gowen Field (BOI), Boise, ID
- 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
- Taxi · to runway
- 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
- Substantial
Cause areas
- Aircraft › Aircraft oper/perf/capability
- Aircraft › Aircraft systems
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The airplane was designed to use differential braking for directional control while taxiing. The pilot reported that while taxiing for departure, the right brake failed. Subsequently, the airplane departed the left side of the taxiway, impacted a pole and went down an embankment, striking an airport perimeter fence. The left composite wing tip was split open and the wing's leading edge had an 8- to 10-inch chordwise rip in it. Postaccident examination of the airplane by a Federal Aviation Administration inspector found that the right brake O-ring in the piston that operates the caliper was hard and flat. When brake fluid was put in the system and the brakes were pumped, the brake fluid was observed to pass directly through the right-hand caliper onto the ground.
Probable cause
The loss of directional control while taxiing due to the failure of the right brake.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record LAX08LA217
- Event ID
- 20080721X01087
- Case number
- LAX08LA217
- 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. 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: d44dd280027cea8d6eb701d0eb16d7cfefda4515b55a177757e1a37092bce4eb; retrieved 2026-09-15T09:56:11.579Z.