# Incident 19960104001299I: Cessna 172N, Tucson, AZ, January 4, 1996

- Type: FAA incident report (Accident/Incident Data System), as reported
- Date: January 4, 1996, 12:10 local time
- Place: Tucson, AZ
- Airport: Tucson International
- Damage: Minor damage
- Phase of flight: Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 32.1171° N, 110.9415° W: Placed by OpenAirDocs at TUCSON INTL (TUS), within about a mile (OpenAirDocs)
- Nearby events: https://openairdocs.org/map.md?lat=32.1171&lon=-110.9415&mi=10
- Aircraft: N6326J, a cancelled registration (https://openairdocs.org/deregistered/N6326J-2018-05-31) (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: 100 total, 25 in this make and model, 38 in the last 90 days
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19960104001299I

## Narrative

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

NARRATIVE: UPON LANDING AT TUCSON INT'L AIRPORT, ON RUNWAY 11L, ^PRIVACY DATA OMITTED^ THIS INCIDENT WAS WITNESSED BY THE FSDO OPERATIONS INSPECTOR WHO IN TURN COUNSELLED THE PILOT ON HOW TO AVOID WAKE TURBULENCE PRODUCED BY HEAVY AIRCRAFT WHEN OPERATIONAL IN AN AIRPORT TRAFFIC AREA. THIS INCIDENT IS CLOSED.

## Other reports on N6326J (1)

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

- [Accident 20150703009909A](https://openairdocs.org/incident/20150703009909A), Jul 3, 2015: Cessna 172N (N6326J), Lubbock, TX, Substantial damage. On July 3, 2015, at 1227, a Cessna CE-172-N aircraft bearing registration number N6326J, registered to hub city aviation inc., was operated by a student pilot…

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.