GAA16CA449 · Cessna 182 Q
Civil Air Patrol Cessna 182 Q · Accident: landing area overshoot
From Fallbrook Community Airpark (L18) to Fallbrook Community Airpark (L18)
Event
- NTSB case
- GAA16CA449
- 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
Cessna 182 Q
- Aircraft type
- Cessna 182
- 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
- N4810N
- Operator
- Civil Air Patrol
- Onboard fatalities
- Unknown
- Route
- From Fallbrook Community Airpark (L18), Fallbrook, CATo Fallbrook Community Airpark (L18), Fallbrook, CA
- Aircraft age
- About 36 years (built 1980)
- 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
- 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
- Landing area overshoot
- 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
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The flight instructor reported that during a Civil Air Patrol evaluation flight, he decided to demonstrate a power off landing to the pilot being evaluated. The flight instructor further reported that the airplane touched down within the first 400 feet of the 2,160-foot runway and reported that the brakes were ineffective during the landing roll. The pilot witness who observed the landing from the left seat reported that he observed heavy braking, some swerving, a loss of control, and the airplane exited the left side of the runway near the departure end of the runway. During the runway excursion, the airplane nosed over and sustained substantial damage to the fuselage, empennage, and the right wing lift strut.
In a Civil Air Patrol online system, the pilot witness reported that over the runway threshold the airspeed was 84 knots, the altitude was 20 feet, and the airplane touchdown zone was 1/2 to 2/3 down the runway, with 1000 feet of runway remaining.
The local flight school provided video surveillance of the landing. The video showed the airplane still airborne while in the camera frame, which was about 700 feet past the runway threshold. The airplane subsequently moved out of camera view and was still airborne. The video did not show the airplane touch down on the runway.
In a post-accident examination four days after the accident by the Federal Aviation Administration (FAA), both brakes were found to be functional.
In a post-accident inspection almost two weeks after the accident by the repair mechanic, it was revealed that the left brake was working, but the right brake was "full of air." The mechanic reported that when the airplane was upside down air can enter into the hydraulic system, so "all bets are off". The mechanic further reported that there were no flat or bald spots on the tires.
Probable cause
The flight instructor's failure to go-around and the subsequent long landing and his failure to maintain directional control, which resulted in a runway excursion.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record GAA16CA449
- Event ID
- 20160826X43408
- Case number
- GAA16CA449
- 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: 9c4987f397f1b50fe664a2ac159f8d4b96fc220406763af9574fa0bfabe3c7f5; retrieved 2026-09-16T04:11:45.189Z.