# Accident 20030114000489A: Cessna R172K, Gigharbor, WA, January 14, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 14, 2003, 07:45 local time
- Place: Gigharbor, WA
- Damage: Substantial damage
- Operating rules: General operating rules (Part 91)
- Location: 47.3311° N, 122.5889° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=47.3311&lon=-122.5889&mi=10
- Aircraft: N1909V, a cancelled registration (https://openairdocs.org/deregistered/N1909V-2013-09-20) (OpenAirDocs)
- Registry model: Cessna R172K (registry code 2072431, https://openairdocs.org/model/cessna-r172k) (OpenAirDocs)
- Registry engine: Continental IO-360 series (registry code 17025, https://openairdocs.org/engine/continental-io-360-series) (OpenAirDocs)
- Reported make and model: CESSNA R172K
- NTSB investigation: [NTSB SEA03FA026](https://openairdocs.org/ntsb/SEA03FA026) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20030114000489A

## Narrative

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

(-23) PILOT INITIALLY REPORTED THAT HE HAD MADE A PRECAUTIONARY LANDING AT (TIW) TACOMA NARROWS AIRPORT DUE TO ENGINE ROUGHNESS. PILOT STATED THE HE NOTICED LOW FUEL LEVEL. THE PILOT STATED THE HE HAD INSPECTED THE FUEL TANKS AND HAD VERIFIED THAT THE RIGHT FUEL TANK WAS EMPTY. PILOT STATED THAT HE PURCHASED FUEL @ PAVCO AND HAD PUT IN 10 GALLONS PER SIDE. PILOT STATED THAT HE HAD PERFORMED A GROUND RUN-UP AND THAT EVERYTHING APPEARED NORMAL PRIOR TO TAKE OFF FROM TIW. PILOT ASSUMED THAT THE ENGINE ROUGHNESS WAS DUE TO FUEL EXHAUSTION IN THE RIGHT TANK AND THE ROUGHNESS HAD OCCURRED WHILE HE WAS IN A LEFT HAND TURN. PILOT THEN STATED THAT @ APPROX. 3000 FEET HE STARTED TO LEVEL OFF WHEN THE ENGINE STARTED TO SURGE. PILOT TRIED VARIOUS PROP GOVERNOR RANGES TO TRY TO SMOOTH OUT THE ROUGHNESS BUT NOTHING SEEMED TO HELP. PILOT STATED THAT HE COULD NOT MAINTAIN POWER OR ALTITUDE. PILOT THEN PICKED OUT A ROAD TO LAND ON WHEN A CAR PULLED OUT IN FRONT OF THE AIRCRAFT. ENGINE PROPELLER CONTACTED THE CAR AT LEAST 3 TIMES AND THE RIGHT GEAR WAS TORN OFF THE AIRCRAFT AT THIS TIME.

## 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 SEA03FA026](https://openairdocs.org/ntsb/SEA03FA026), Jan 14, 2003: Cessna 172K (N1909V), Gig Harbor, WA, substantial damage. Probable cause: The loss of engine power in the climb due to the fracture of the number seven engine crankshaft cheek due to the propagation of a fatigue crack initiation point. Factors include a vehicle pulling…

## Other reports on N1909V (1)

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

- [Accident 19990521044059A](https://openairdocs.org/incident/19990521044059A), May 21, 1999: Cessna R172K (N1909V), Aurora, OR, No damage. (-23) The PIC was making a full flap landing at Aurora airport. The aircraft stalled approx. 5 feet above the runway causing the a/c to bounce. The PIC tried…

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.