# Incident 20060602009649I: Cessna R182, San Luis Obispo, CA, June 2, 2006

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: June 2, 2006, 15:13 local time
- Place: San Luis Obispo, CA
- Airport: San Luis Obispo County
- Damage: Minor damage
- Phase of flight: Level Off Touchdown
- Operating rules: General operating rules (Part 91)
- Location: 35.2373° N, 120.6426° W: Placed by OpenAirDocs at SAN LUIS OBISPO COUNTY RGNL (SBP), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=35.2373&lon=-120.6426&mi=10
- Aircraft: N171MH, registered now (https://openairdocs.org/aircraft/N171MH) (OpenAirDocs)
- Registry model: Cessna R182 (registry code 2072734, https://openairdocs.org/model/cessna-r182) (OpenAirDocs)
- Registry engine: Lycoming 0-540 series (registry code 41532, https://openairdocs.org/engine/lycoming-0-540-series) (OpenAirDocs)
- Reported make and model: CESSNA R182
- People aboard: 1
- Fatal injuries: 0
- Pilot flight hours: 960 total, 5 in this make and model, 17 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20060602009649I

## Narrative

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

(-23) THE PILOT ENCOUNTERED A HARD LANDING AT THE SAN LUIS OBISPO, CA AIRPORT. THE NOSE LANDING GEAR TIRE BLEW CAUSING DAMAGE TO THE NOSE WHEEL ASSEMBLY. FURTHER INVESTIGATION REVEALED THE NOSE LANDING GEAR FORK ASSEMBLY WAS ALSO DAMAGED, THEREFORE THE LOWER PORTION (PISTON ASSEMBLY) OF THE LANDING REQUIRED REPLACEMENT.

## Other reports on N171MH (1)

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

- [Incident 20080915845789I](https://openairdocs.org/incident/20080915845789I), Sep 15, 2008: Cessna R182 (N171MH), Brigham City, UT, Minor damage. (-23) The pilot stated that he and another pilot were going to practice landings. They departed bountiful airport and then they flew to the Brigham City…

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.