# Accident 19960301003369A: Cessna 172D, Gainesville, FL, March 1, 1996

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: March 1, 1996, 19:45 local time
- Place: Gainesville, FL
- Airport: Gainesville Regional Airport
- Damage: Destroyed
- Phase of flight: Initial Approach-IFR
- Operating rules: General operating rules (Part 91)
- Location: 29.5905° N, 82.0796° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=29.5905&lon=-82.0796&mi=10
- Aircraft: N2456U, a cancelled registration (https://openairdocs.org/deregistered/N2456U-2014-09-22) (OpenAirDocs)
- Registry model: Cessna 172D (registry code 2072410, https://openairdocs.org/model/cessna-172d) (OpenAirDocs)
- Registry engine: Continental 0-300 series (registry code 17022, https://openairdocs.org/engine/continental-0-300-series) (OpenAirDocs)
- Reported make and model: CESSNA 172D
- Reported engine: CONT O300D
- People aboard: 2
- Fatal injuries: 2
- Pilot flight hours: 409 total, 367 in this make and model, 257 in the last 90 days
- NTSB investigation: [NTSB MIA96FA089](https://openairdocs.org/ntsb/MIA96FA089) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960301003369A

## Narrative

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

LOST CONTROL DURING INITIAL ILS APPROACH. STRUCK TREES. GYROS SHOWED NO SCORING. NO OTHER ANOMALIES. LACKED VECTORS

## 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 MIA96FA089](https://openairdocs.org/ntsb/MIA96FA089), Mar 2, 1996: Cessna 172D (N2456U), Hawthorne, FL, destroyed, 2 fatal. Probable cause: the pilot's failure to maintain the proper glidepath during an instrument approach.

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.