# Incident 19810311064839I: Cessna 177, Carlsbad, CA, March 11, 1981

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: March 11, 1981, 19:04 local time
- Place: Carlsbad, CA
- Airport: Palomar Tower
- Damage: Minor damage
- Phase of flight: Normal Cruise
- Operating rules: General operating rules (Part 91)
- Location: 33.1581° N, 117.3506° W: Placed by OpenAirDocs: center of Carlsbad, CA, within about 6 miles (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=33.1581&lon=-117.3506&mi=10
- Aircraft: N35105, a cancelled registration (https://openairdocs.org/deregistered/N35105-1989-03-08) (OpenAirDocs)
- Registry model: Cessna 177B (registry code 2073708, https://openairdocs.org/model/cessna-177b) (OpenAirDocs)
- Reported make and model: CESSNA 177
- Fatal injuries: 0
- Pilot flight hours: 3,000 total, 1,220 in this make and model, 18 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19810311064839I

## Narrative

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

ZA ENGINE QUIT, RAN OUT OF FUEL LANDED AT NIGHT ON ROAD.

## Other reports on N35105 (3)

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

- [Accident 19850922046899A](https://openairdocs.org/incident/19850922046899A), Sep 22, 1985: Cessna 177B (N35105), Lolo Pass, ID, Destroyed, 2 fatal. Stalled while maneuvering to landing site after engine quit due to fuel exhaustion. Fuel not checked visually.
- [Accident 19830308008529A](https://openairdocs.org/incident/19830308008529A), Mar 8, 1983: Cessna 177B (N35105), Arvin, CA, Substantial damage. Crash occurred during emergency landing after engine quit from fuel exhaustion.
- [Incident 19780916019269I](https://openairdocs.org/incident/19780916019269I), Sep 16, 1978: Cessna 177 (N35105), San Diego, CA. Pilot lost communication in IFR conditions. Reached VFR conditions on top, flew to another airport.

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.