# Accident 20040119000969A: Cessna 172K, Grass Valley, CA, January 19, 2004

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: January 19, 2004, 18:20 local time
- Place: Grass Valley, CA
- Airport: Nevada County Airpark
- Damage: Destroyed
- Phase of flight: Approach
- Operating rules: General operating rules (Part 91)
- Location: 39.2169° N, 121.0003° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=39.2169&lon=-121.0003&mi=10
- Aircraft: N99LR, a cancelled registration (https://openairdocs.org/deregistered/N99LR-2004-03-06) (OpenAirDocs)
- Registry model: Cessna 172K (registry code 2072430, https://openairdocs.org/model/cessna-172k) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172K
- Reported engine: LYC O320E2D
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 1,147 total, 1,147 in this make and model, 30 in the last 90 days
- NTSB investigation: [NTSB LAX04FA096](https://openairdocs.org/ntsb/LAX04FA096) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20040119000969A

## Narrative

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

(-23) AIRCRAFT CRASHED INTO TREES 1 MILE SOUTH EAST FROM GRASS VALLEY AIRPORT FATALLY INJURING BOTH OCCUPANTS ON BOARD (BIOHAZARD AREA). THE AIRCRAFT WAS SEVERELY DESTROYED. NO INDICATIONS OF FIRE.

## 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 LAX04FA096](https://openairdocs.org/ntsb/LAX04FA096), Jan 20, 2004: Cessna 172K (N99LR), Grass Valley, CA, destroyed, 2 fatal. Probable cause: the pilot's continued visual flight into instrument meteorological conditions and failure to maintain an adequate terrain/object clearance altitude. Also causal was the pilot's improper in-flight…

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.