# Accident 20031124033609A: Cessna 172P, Scottsdale, AR, November 24, 2003

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: November 24, 2003, 16:00 local time
- Place: Scottsdale, AR
- Damage: Substantial damage
- Phase of flight: Sfl Final Approach
- Operating rules: General operating rules (Part 91)
- Location: 33.6511° N, 111.5958° W: From the FAA
- Nearby events: https://openairdocs.org/map.md?lat=33.6511&lon=-111.5958&mi=10
- Aircraft: N97056, a cancelled registration (https://openairdocs.org/deregistered/N97056-2013-06-05) (OpenAirDocs)
- Registry model: Cessna 172P (registry code 2072436, https://openairdocs.org/model/cessna-172p) (OpenAirDocs)
- Registry engine: Lycoming 0-320 series (registry code 41508, https://openairdocs.org/engine/lycoming-0-320-series) (OpenAirDocs)
- Reported make and model: CESSNA 172P
- Reported engine: LYC O320D2J
- Fatal injuries: 0
- Pilot flight hours: 2,300 total, 1,250 in this make and model, 97 in the last 90 days
- NTSB investigation: [NTSB LAX04LA053](https://openairdocs.org/ntsb/LAX04LA053) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/20031124033609A

## Narrative

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

(-23) INVESTIGATION OF THE ACCIDENT THAT INVOLVED THE OPERATION OF A CESSNA 172 AIRCRAFT, N97056, ON AN INSTRUCTIONAL FLIGHT NEAR SCOTTSDALE, ARIZONA AT APPROXIMATELY 4:00 PM ON NOVEMBER 24, 2003 REVEALED THAT THE FLIGHT INSTRUCTOR NEGLECTED HIS INSTRUCTOR RESPONSIBILITIES BY NOT PROVIDING REASONABLE AND PRUDENT SUPERVISION OF THE INSTRUCTIONAL FLIGHT. HE ALLOWED THE INSTRUCTIONAL AIRCRAFT TO DESCEND SO LOW DURING A SIMULATED EMERGENCY LANDING THAT A GO-AROUND MANEUVER COULD NOT BE ACCOMPLISHED IN TIME TO AVOID A COLLISION WITH THE GROUND.

## 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 LAX04LA053](https://openairdocs.org/ntsb/LAX04LA053), Nov 24, 2003: Cessna 172P (N97056), Fountain Hills, AZ, substantial damage. Probable cause: The flight instructor's delayed remedial action and inadequate altitude during a go-around following a simulated forced landing, which resulted in an in-flight collision with terrain.

## Other reports on N97056 (3)

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

- [Accident 20020726017129A](https://openairdocs.org/incident/20020726017129A), Jul 26, 2002: Cessna 172P (N97056), Mesa, AZ, Minor damage. (.19) On July 26, 2002, at 1600 mountain standard time, a Cessna 172P, N97056, taxied into a standing Cessna 152, N152BR, in the run-up area at Falcon field,…
- [Incident 20000923030249I](https://openairdocs.org/incident/20000923030249I), Sep 23, 2000: Cessna 172P (N97056), Tucson, AZ, Minor damage. (23)Pilot stated that while taxing on taxiway A7 at Tucson, he inadvertently ran over a taxi light causing damage to the light and minor damage to the wheel…
- [Incident 19870721044379I](https://openairdocs.org/incident/19870721044379I), Jul 21, 1987: Cessna 172P (N97056), Imperial, CA, Minor damage. Solo student landing in a crosswind allowed the aircraft to touchdown with a wheel off the runway. Nosed over.

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.