# Accident 20001012038689A: Cessna 170B, San Carlos, CA, October 12, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: October 12, 2000, 11:25 local time
- Place: San Carlos, CA
- Airport: San Carlos Airport
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 37.4905° N, 122.2605° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=37.4905&lon=-122.2605&mi=10
- Aircraft: N2562D, registered now (https://openairdocs.org/aircraft/N2562D) (OpenAirDocs)
- Registry model: Cessna 170B (registry code 2072306, https://openairdocs.org/model/cessna-170b) (OpenAirDocs)
- Registry engine: Continental IO-360-D (registry code 17149, https://openairdocs.org/engine/continental-io-360-d) (OpenAirDocs)
- Reported make and model: CESSNA 170B
- NTSB investigation: [NTSB LAX01LA010](https://openairdocs.org/ntsb/LAX01LA010) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20001012038689A

## Narrative

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

(-23) CESSNA N2562D LANDED ON RUNWAY 30 AT SAN CARLOS AIRPORT, DURING THE LANDING ROLL THE A/C VEERED TO THE RIGHT, THE PILOT THEN APPLIED FULL BRAKES CAUSING THE AIRCRAFT TO FLIP OVER AND LANDED INVERTED. A COPY OF THIS REPORT WILL BE FORWARDED TO THE OPERATIONS UNIT FOR FURTHER EVALUATION.

## 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 LAX01LA010](https://openairdocs.org/ntsb/LAX01LA010), Oct 12, 2000: Cessna 170B (N2562D), San Carlos, CA, substantial damage. Probable cause: The pilot's improper and excessive application of brakes resulting from his failure to maintain directional control during landing rollout.

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.