20030920028029A

Accident · Destroyed

FAA accident report · Cessna 182A · Georgetown, CA · September 20, 2003

Date
September 20, 2003 · 14:30 local
Place
Georgetown, CA
Airport
Georgetown Airport
Phase of flight
Roll-Out (Fixed Wing)
Operating rules
General operating rules (Part 91)
Damage
Destroyed
Aircraft
N9921B
NTSB investigation
NTSBLAX03LA293
Reported as
Cessna 182A
Fatal injuries
0
Pilot’s flight hours
478 total300 in this make and model30 in the last 90 days

From the FAA’s Accident/Incident Data System (AIDS), through its Aviation Safety Information Portal, as reported. The NTSB investigates accidents separately, and its record of an accident is the fuller one. The aircraft is matched to the registry by N-number and event date, checked against the reported make and model; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

What happened

The FAA’s narrative, in sentence case. The FAA writes it in capitals and removes private details.

(-23) 1. Landing approach was high and fast as per the pilot statement. 2. Touchdown point was beyond the center point of the runway based upon witness statements. 3. Adequate braking was not available since the full weight of the airplane was not on the wheels as evidenced by the tire marks on the runway. 4. Decision to execute go-around was excessively delayed while trying to apply maximum braking.

As the FAA filed it

(-23) 1. LANDING APPROACH WAS HIGH AND FAST AS PER THE PILOT STATEMENT. 2. TOUCHDOWN POINT WAS BEYOND THE CENTER POINT OF THE RUNWAY BASED UPON WITNESS STATEMENTS. 3. ADEQUATE BRAKING WAS NOT AVAILABLE SINCE THE FULL WEIGHT OF THE AIRPLANE WAS NOT ON THE WHEELS AS EVIDENCED BY THE TIRE MARKS ON THE RUNWAY. 4. DECISION TO EXECUTE GO-AROUND WAS EXCESSIVELY DELAYED WHILE TRYING TO APPLY MAXIMUM BRAKING.

NTSB investigation

The NTSB’s investigation of this event, with its probable cause and findings. Matched to this report by N-number and date.