# N100UW: 1977 Cessna 340A, registration cancelled 2024-01-13

- Type: Cancelled registration (FAA registry, deregistered aircraft)
- Cancelled: January 13, 2024
- Status when cancelled: Registration pending, canceled
- Airframe: [Cessna 340A](https://openairdocs.org/model/cessna-340a) (registry code 2076405)
- Engine: [Continental TSIO-520 series](https://openairdocs.org/engine/continental-tsio-520-series) (registry code 17040)
- Data sheets: [TCDS 3A25](https://openairdocs.org/tcds/3A25), [TCDS E8CE](https://openairdocs.org/tcds/E8CE) (OpenAirDocs)
- Serial number: 340A0259
- Year built: 1977
- Type of aircraft: Fixed wing multi engine
- Engine type: Reciprocating
- Airworthiness: Standard, normal
- Airworthiness date: February 17, 1977
- Last registry action: October 12, 2022
- Mode S code: A0068B
- Location: [Madera, CA](https://openairdocs.org/faa-place/CA/Madera)
- Owner type: Individual
- Owner's area on the map: 36.9181° N, 120.1859° W: Placed by OpenAirDocs at the center of ZIP code 93637, within about 9 miles (OpenAirDocs). The owner's mailing address, not where the aircraft was based
- The mark today: https://openairdocs.org/aircraft/N100UW
- FAA registry: https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=100UW
- Page: https://openairdocs.org/deregistered/N100UW-2024-01-13

From the FAA registry file of November 5, 2026, cancelled registrations. Owners' street addresses are left out. The Mode S code belongs to the N-number, not the airframe.

ADs and bulletins for the Cessna 340A: https://openairdocs.org/model/cessna-340a.md

## NTSB investigations (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 LAX03LA149](https://openairdocs.org/ntsb/LAX03LA149), Apr 23, 2003: Cessna 340A (N100UW), Boulder City, NV, substantial damage. Probable cause: the airport committee members failure to repair or mark the faulty telephone junction box cover as a hazard. A factor in the accident was the inadequate notification process of the airport and city…

## FAA accident and incident reports (3)

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.

- [Incident 20221122018169I](https://openairdocs.org/incident/20221122018169I), Nov 22, 2022: Cessna 340A (N100UW), Riverside, CA, Minor damage. [privacy data omitted]Landed on runway 27 at 1557 local 11/22/2022. Pilot taxied off runway 27 and turned left on to runway 16/34. After turn notified tower of…
- [Accident 20030424004209A](https://openairdocs.org/incident/20030424004209A), Apr 24, 2003: Cessna 340A (N100UW), Boulder City, NV, Substantial damage. (-23) During taxi from hanger to fuel pumps aircraft was on taxiway when a telephone man hole cover broke as aircraft weight was on it. Man hole cover was…
- [Incident 19900722055499I](https://openairdocs.org/incident/19900722055499I), Jul 22, 1990: Cessna 340A (N100UW), Carlsbad, CA. Smoke in cockpit. Priority handling for return. Two capped wires were loose and sparking.

---
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.