# NTSB LAX02LA133: Cessna 172S, N3512T, Phoenix, AZ, April 5, 2002 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: April 4, 2002, 18:15 local (Apr 5, 2002, 01:15 UTC) - Place: Phoenix, AZ - Coordinates: 33.688331, -112.083335 - Nearby events: https://openairdocs.org/map.md?lat=33.6883&lon=-112.0833&mi=10 - Phase of flight: [Landing](https://openairdocs.org/ntsb-phases/550) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report October 24, 2002 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 54511 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02LA133 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/54511/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=54511 - Page: https://openairdocs.org/ntsb/LAX02LA133 ## Probable cause the pilot flaring the airplane too high above the runway causing a stall and resulting in the hard landing. Factors relating to the accident were the light conditions (dusk) and the pilot's lack of total experience in the type of airplane. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Hard landing, landing - flare - high, pilot in command (cause) - stall/mush - encountered, pilot in command (cause) - lack of total experience in type of aircraft, pilot in command (contributing factor) - light condition - dusk (contributing factor) ## Analysis The pilot said that everything was fine through the traffic pattern to the flare for landing. The pilot said, "During flare, blinded momentarily by sunlight, difficulties to judge altitude above RWY (runway) correctly. Flared too high." The pilot said he kept the nose of the airplane up to protect the nosewheel. He said, "... speed bled off ... resulting in heavy bumps onto the RWY together with stall warning." The pilot said that after 3 or 4 bumps, the airplane stayed on the runway. The pilot then taxied to the ramp. The pilot concluded, "I simply landed the airplane too high due to the lighting conditions and my landing picture based on my experience landing an Airbus A340." The pilot also concluded in recommendations he provided that he get more landings "to get the right picture during (the) flare." A post-accident examination of the airplane revealed no anomalies. ## Factual narrative On April 4, 2002, approximately 1815 mountain standard time, a Cessna 172S, N3512T, piloted by a foreign-based airline transport pilot, was substantially damaged during a hard landing at the Phoenix Deer Valley Airport (DVT), Phoenix, Arizona. Visual meteorological conditions prevailed at the time of the accident. The personal flight was being conducted on a visual flight rules flight plan under the provisions of Title 14 Code of Federal Regulations Part 91. The pilot and passenger on board the airplane reported no injuries. The cross-country flight originated at Grand Canyon, Arizona, at 1705. The pilot said that everything was fine through the traffic pattern to the flare for landing. The pilot said, "During flare, blinded momentarily by sunlight, difficulties to judge altitude above RWY (runway) correctly. Flared too high." The pilot said he kept the nose of the airplane up to protect the nosewheel. He said, "... speed bled off ... resulting in heavy bumps onto the RWY together with stall warning." The pilot said that after 3 or 4 bumps, the airplane stayed on the runway. The pilot then taxied to the ramp. The pilot concluded, "I simply landed the airplane too high due to the lighting conditions and my landing picture based on my experience landing an Airbus A340." The pilot also concluded in recommendations he provided that he get more landings "to get the right picture during (the) flare." A post-accident inspection of the airplane showed the airplane's nose gear pushed aft into the firewall. The lower part of the firewall was bent inward and aft. Flight control continuity was confirmed. An examination of the airplane's engine, engine controls, and other systems revealed no anomalies. ## Aircraft - Registration: [N3512T](https://openairdocs.org/aircraft/N3512T), registered now, S/N 172S8883 (OpenAirDocs) - Reported make and model: Cessna 172S - Registry model: [Cessna 172S](https://openairdocs.org/model/cessna-172s) (registry code 2072439) (OpenAirDocs) - Category: Airplane - Serial number: 172S8883 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Westwind Aviation - Airworthiness certificate: Standard, Normal - Departed: GCN, Grand Canyon, AZ - Destination: DVT, Phoenix, AZ - Flight plan: VFR - Airport: DVT, Phoenix Deer Valley Airport, runway 25L, 8,208 × 100 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 35; injuries: none; airline transport, private, foreign; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 2; last flight review March 22, 2002; seat: left; flight hours: 7,087 total, 10 in this make and model, 12 as pilot in command, 225 in the last 90 days, 79 in the last 30 days, 17 in the last 24 hours ## Weather - Conditions: Visual (VMC), Dusk - Wind: 270° at 8 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 90 °F, dew point 27 °F - Altimeter: 29.87 inHg - Observed at: PHX, 15 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20020405007489A](https://openairdocs.org/incident/20020405007489A), Apr 5, 2002: Cessna 172S, Phoenix, AZ, Substantial damage. (.4) The pilot said that everything was fine through the traffic pattern to the flare for landing. The pilot said, "during flare, blinded momentarily by… ## Docket (4 files) The files NTSB released with the investigation on September 11, 2002, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=54511. 501 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 392 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40428191&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Redacted.PDF - Supplement S (item 2, .PDF, 21 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40161969&FileExtension=.PDF&FileName=Supplement%20S-Master.PDF - Sun and Moon Data, Phoenix, AZ on 4/4/2002 (item 3, .PDF, 15 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40162284&FileExtension=.PDF&FileName=Sun%20and%20Moon%20Data,%20Phoenix,%20AZ%20on%204%2F4%2F2002-Master.PDF - Airport Diagram (item 4, .PDF, 74 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40162287&FileExtension=.PDF&FileName=Airport%20Diagram-Master.PDF 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. --- 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.