Executive Flight Services Cessna 525 B accident
Cessna 525 B · Accident: runway excursion during landing
From Washington Dulles International Airport (IAD) to an unrecorded destination
Event
- NTSB case
- ERA22LA148
- 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
- 0
- 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
- Charter & commuter
- 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
Cessna 525 B
- Aircraft type
- Cessna 525
- 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
- N22AU
- Operator
- Executive Flight Services
- Onboard fatalities
- Unknown
- Route
- From Washington Dulles International Airport (IAD), Dulles, VATo not recorded
- Aircraft age
- About 13 years (built 2009)
- 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 135: Air Taxi & Commuter
- 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
- Runway excursion
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.
NTSB narrative
The flight crew reported they flew a normal flight and a stabilized approach in gusty wind conditions. Performance data indicated they would require about 3,000 ft of runway for landing on the 6,995 ft long runway, and they added 5 knots (kts) to the approach speed due to the gusts. Data indicated that the airplane landed in the touchdown zone and at an appropriate airspeed of 110 kts (104 kts groundspeed); however, the pilot’s and co-pilot’s application of brakes was unsuccessful in achieving sufficient braking action. The airplane departed the runway at a groundspeed of 58 kts and came to rest against a perimeter fence 450 ft past the runway. A witness stated the airplane landed long; however, his distance from the runway and his angle of view of the airplane may have prevented an accurate assessment. Although the airplane flight manual states that if the brake system or antiskid fails, the pilot(s) are to attempt to pull the emergency brake, the pilots were unable to locate the emergency brake and instead pulled the parking brake. Although an examination of the braking system failed to find an anomaly, a performance study revealed that during the ground rollout the deceleration was primarily due to aerodynamic drag and free rolling “unbraked” wheel friction for about 5,000 ft and that there was virtually no evidence of deceleration due to hydraulic or pneumatic wheel braking during the rollout. However, the pilots’ inability to locate and use the emergency brake contributed to the insufficient braking. The crew failed to immediately recognize the issue and locate and utilize the emergency brake for supplemental braking authority.
Probable cause
And undetermined failure of the brake system. Contributing to the accident was the failure of the pilots to locate and operate the emergency brake control, which resulted in a runway excursion and collision with terrain and an object.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA148
- Event ID
- 20220308104737
- Case number
- ERA22LA148
- 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, cause areas. 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: 7b90e437a423ad3257c1660b612eec10730e6ba03ddbc8210ce0fb0702e24122; retrieved 2026-09-16T15:01:13.592Z.