# Accident 19991217045189A: Cessna 172N, Concord, CA, December 17, 1999

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: December 17, 1999, 10:24 local time
- Place: Concord, CA
- Airport: Buchanan Field
- Damage: Substantial damage
- Phase of flight: Takeoff Ground Roll
- Operating rules: General operating rules (Part 91)
- Location: 38.0001° N, 122.0303° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=38.0001&lon=-122.0303&mi=10
- Aircraft: N738UA, a cancelled registration (https://openairdocs.org/deregistered/N738UA-2017-07-20) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- Reported engine: LYC O320H2AD
- Fatal injuries: 0
- Pilot flight hours: 40,000 total
- NTSB investigation: [NTSB LAX00LA054](https://openairdocs.org/ntsb/LAX00LA054) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19991217045189A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

(.4) ON DECEMBER 17, 1999, AT 1024 HOURS PACIFIC STANDARD TIME, A CESSNA 172N, N738UA, OPERATED BY THE PILOT WAS SUBSTANTIALLY DAMAGED DURING A TAKEOFF ATTEMPT AT CONCORD, CALIFORNIA, WHEN IT RAN OFF THE DEPARTURE END OF THE RUNWAY AND COLLIDED WITH A FENCE.  THE AIRLINE TRANSPORT PILOT, THE SOLE OCCUPANT, RECEIVED MINOR INJURIES.  VISUAL METEOROLOGICAL CONDITIONS PREVAILED FOR THE PERSONAL FLIGHT OPERATING UNDER 14 CFR PART 91 AND NO FLIGHT PLAN WAS FILED.  THE FLIGHT WAS DESTINED FOR NAPA, CALIFORNIA.                AFTER THE ACCIDENT THE PILOT STATED TO A FEDERAL AVIATION ADMINISTRATION INSPECTOR, WHO RESPONDED TO THE SCENE, THAT HE HAD FAILED TO REMOVE THE CONTROL GUST LOCK PRIOR TO THE TAKEOFF ATTEMPT. IN THE PILOT'S INSURANCE COMPANY REPORT HE ALSO STATED THAT HE FAILED TO REMOVE THE GUST LOCK DURING THE TAKEOFF ROLL. HE SAID HE REDUCED THE THROTTLE AND OVER FLEW THE AIRPORT FENCE AND LANDED ON A ROAD NEAR THE RUNWAY. THE PILOT FILED A PARTIAL AIRCRAFT ACCIDENT REPORT WITHOUT A STATEMENT.                                                                                                                                                                                               (-23) PILOT TOOK OFF AND UPON REACHING THE END OF THE RUNWAY HE REALIZES THA THE GUST LOCK PIN IS INSTALLED. PILOT STATED THAT HE ATTEMPTED TO REMOVE IT BUT DID NOT SUCCEED AND THE A/C IMPACTED THE GROUND 440 FEET FROM THE END OF RUNWAY 32L.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB LAX00LA054](https://openairdocs.org/ntsb/LAX00LA054), Dec 17, 1999: Cessna 172N (N738UA), Concord, CA, substantial damage. Probable cause: the pilot's failure to use a checklist and remove the control gust lock.

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft 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. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.