# Incident 19961006037669I: Cessna 172P, Sacramento, CA, October 6, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: October 6, 1996, 17:20 local time
- Place: Sacramento, CA
- Airport: Sacramento Executive Airport
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 38.5129° N, 121.4933° W: Placed by OpenAirDocs at SACRAMENTO EXEC (SAC), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=38.5129&lon=-121.4933&mi=10
- Aircraft: N54661, registered now (https://openairdocs.org/aircraft/N54661) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- People aboard: 3
- Fatal injuries: 0
- Pilot flight hours: 54 total, 4 in this make and model, 16 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19961006037669I

## Narrative

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

NARRATIVE: PILOT WAS CLEARED TO LAND ON RUNWAY 34 AT SACRAMENTO EXECUTIVE AIRPORT. SHE STATED SHE WAS USING FULL FLAPS. ON LANDING THE PILOT FAILED TO FLAIR AND THE AIRCRAFT LANDED ON THE NOSE WHEEL. THE AIRCRAFT SUBSEQUENTLY FLEW AGAIN AND A PORPOISING EFFECT OCCURRED. THE AIRCRAFT BOUNCED A TOTAL OF THREE TIMES PRIOR TO COMING TO A STOP. THE PILOT THEN TAXIED THE AIRCRAFT OFF THE RUNWAY AND TO THE PARKING AREA.

## Other reports on N54661 (1)

Matched to the same aircraft by N-number and date.

- [Accident 20060211013592A](https://openairdocs.org/incident/20060211013592A), Feb 11, 2006: Cessna 172P (N54661), Sacramento, CA, Minor damage. (-23) Aircraft was in runup area at Sacramento exec airport when another aircraft taxied into it, striking the vertical structure.

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.