ERA22LA272 · Cessna 414
Cessna 414 · Accident: system/component malfunction/failure (non-power) during landing
From Leesburg Executive Airport (JYO) to an unrecorded destination
Event
- NTSB case
- ERA22LA272
- 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
- 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
Cessna 414
- Aircraft type
- Cessna 414
- 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
- N1996G
- Operator
- Ertel Caiolinn Chelsea
- Onboard fatalities
- Unknown
- Route
- From Leesburg Executive Airport (JYO), Leesburg, VATo not recorded
- Aircraft age
- About 48 years (built 1974)
- 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
- 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
- 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
No findings designated as a cause are recorded in the NTSB data yet.
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
According to the pilot, she performed the approach at the airplane’s reference landing speed (Vref) plus 10 knots. The airspeed adjustment and the gusting conditions resulted in a touchdown 1,000 ft beyond the touchdown zone on a 4,002 ft-long runway. The pilot applied the brakes with no response, ultimately guiding the airplane to the left at the departure end to avoid lights and other infrastructure. The airplane traveled into the runway’s grass apron, descended an embankment, and came to rest upright with substantial damage to the nose and right wing. The cockpit carpet and panels, as well as an exterior access panel just aft of the nose landing gear bay, were removed and revealed hydraulic (brake) fluid in the area. The nut that secured the 45° fitting to the 90° fitting of the brake hose at the pilot’s right brake master cylinder was found to be loose. According to the airplane’s Service Manual, the service interval for “Brake System Plumbing – Inspect for leaks, hoses for bulges and deterioration…” was after the airplane’s first 100 hours, and then “Every 200 hours” and “Every 12 [months]” thereafter. The most recent annual inspection was performed 12 months, 9 days, and 126.1 aircraft hours before the accident. While the airplane was 9 days past the manufacturer’s recommended inspection interval, the inspection required by regulations was not due for 3 weeks.
Probable cause
Loss of braking authority due to a loosened brake line fitting for reasons that could not be determined, which resulted in a runway overrun.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA22LA272
- Event ID
- 20220620105279
- Case number
- ERA22LA272
- 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: ddbdc1cfdbe0f3cbdb8ba61aac9c9e8056925381754bafca29f9af28215921f8; retrieved 2026-09-16T15:20:40.629Z.