# Accident 20001102019129A: Cessna 172N, Spangle, WA, November 2, 2000

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 2, 2000, 19:00 local time
- Place: Spangle, WA
- Damage: No damage
- Operating rules: General operating rules (Part 91)
- Location: 47.4395° N, 117.3500° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=47.4395&lon=-117.3500&mi=10
- Aircraft: N734UW, registered now (https://openairdocs.org/aircraft/N734UW) (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
- NTSB investigation: [NTSB SEA01LA013](https://openairdocs.org/ntsb/SEA01LA013) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20001102019129A

## Narrative

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

(-23)AIRMAN ATEEMPTED A LANDING AT A PRIVATE UNLIGHTED GRASS STRIP AFTER DARK. VEHICLE LIGHTS WERE POSITIONED TO ILLUMINATE THE APPROACH THRESHOLD.  LANDING APPROACH BEYOND THRESHOLD HOWEVER HAD NO LIGHTS OF ANY KIND (RESIDENTIAL LIGHTS, STREET LIGHTS, ETC.) AVAILABLE IN THE DIRECTION OF INTENDED LANDING.  AIRMAN MADE TWO PASSES TO IDENTIFY THE LANDING AREA AND THEN ON THE THIRD PASS ATTEMPTED TO LAND THE AIRCRAFT.  AIRMAN STATED HE "FELT HIGH" AND LANDED WITH FULL FLAPS, INITIATING A SLIP MANEUVER TO INCREASE ALTITUDE LOSS.  LANDING WAS LONG AND OCCURRED LESS THAN 300 FEET FROM THE FAR END OF THE LADNING RUNWAY.  AIRMAN LANDED AIRCRAFT APPROXIMATELY 30 FEET FROM THE EDGE OF THE RUNWAY IN A PLOWED DIRT FIELD ADJACENT TO THE RUNWAY.  THE LANDING GEAR PROMPTLY DUG INTO THE SOFT DIRT AND THE AIRCRAFT FLIPPED OVER AND REMAINED UPSIDE DOWN.

## 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 SEA01LA013](https://openairdocs.org/ntsb/SEA01LA013), Nov 3, 2000: Cessna 172N (N734UW), Spangle, WA, substantial damage. Probable cause: The pilot's inadequately executed remedial action and his failure to ensure that the aircraft touched down at the proper location. Factors include a dark night, an unlighted runway, and trees off the…

## Other reports on N734UW (1)

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

- [Incident 19930811038709I](https://openairdocs.org/incident/19930811038709I), Aug 11, 1993: Cessna 172N (N734UW), Deer Park, WA. Engine lost power. Forced landing in field. Magneto impulse coupling spring had failed.

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.