# Accident 20040302005449A: Cessna 172N, Tacoma, WA, March 2, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 2, 2004, 21:14 local time
- Place: Tacoma, WA
- Airport: Tacoma Naarrows Airport
- Damage: Substantial damage
- Phase of flight: Initial Approach-IFR
- Operating rules: General operating rules (Part 91)
- Location: 47.2689° N, 122.5667° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=47.2689&lon=-122.5667&mi=10
- Aircraft: N75844, registered now (https://openairdocs.org/aircraft/N75844) (OpenAirDocs)
- Registry model: Cessna 172N (registry code 2072434, https://openairdocs.org/model/cessna-172n) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172N
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 500 total, 250 in this make and model
- NTSB investigation: [NTSB SEA04LA048](https://openairdocs.org/ntsb/SEA04LA048) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040302005449A

## Narrative

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

(-23) PILOT WAS PRACTICING ILS APPROACHES AT THE TACOMA NARROWS AIRPORT (TIW). ON THE THIRD ILS THE LEFT WING STRUCK A TREE. AFTER HEARING A "THUMP" SOUND THE PILOT EXECUTED A GO AROUND AND NOTING NO ABNORMAL FLIGHT CHARACTERISTICS, ELECTED TO FLY THE AIRCRAFT BACK TO HIS HOME BASE AIRPORT, BREMERTON, WA (PWT). PILOT WAS FLYING UNDER THE HOOD AND HAD A SAFETY PILOT IN THE RIGHT SEAT. INSPECTION OF AIRCRAFT BY A FAA MAINTENANCE INSPECTOR REVEALED SUBSTANTIAL DAMAGE TO THE LEFT HAND WING LEADING EDGE AND MAIN SPAR OUTBOARD OF WING STRUT ATTACH POINT. MAIN SPAR APPEARS TO BE BENT. TESTING OF THE GLIDESLOPE INSTALLED IN THE AIRCRAFT REVEALED THE EQUIPMENT TO HAVE A VERY LOW SENSITIVITY RENDERING IT VERY INACCURATE.

## 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 SEA04LA048](https://openairdocs.org/ntsb/SEA04LA048), Mar 3, 2004: Cessna 172N (N75844), Gig Harbor, WA, substantial damage. Probable cause: The pilot's failure to follow the published IFR procedure resulting in failure to maintain clearance from objects during an instrument approach. Trees and an inoperative glide slope receiver were…

## Other reports on N75844 (2)

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

- [Incident 19970327011469I](https://openairdocs.org/incident/19970327011469I), Mar 27, 1997: Cessna 172N (N75844), Medford, OR, Minor damage. Narrative: pilot departed eugene, OR to redding, CA. While over Medford, OR the engine ran excessively rough. Pilot declared emergency and ground rescue…
- [Accident 19791031043089A](https://openairdocs.org/incident/19791031043089A), Oct 31, 1979: Cessna 172N (N75844), Truckee, NV, Substantial damage. Airplane stalled above runway on high level-off. Aircraft dropped to runway. Flipped over.

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.