# NTSB LAX03LA091: Cessna 172S, N3550X, Scottsdale, AZ, February 21, 2003 - Type: NTSB accident investigation - Classification: Accident · Serious injuries · Limited investigation · Final report - Date: February 20, 2003, 17:20 local (Feb 21, 2003, 00:20 UTC) - Place: Scottsdale, AZ - Coordinates: 33.626945, -111.900001 - Nearby events: https://openairdocs.org/map.md?lat=33.6269&lon=-111.9000&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: Serious injuries - Injuries: 1 serious - Status: Completed, report December 28, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 56525 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX03LA091 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/56525/pdf - Page: https://openairdocs.org/ntsb/LAX03LA091 ## Probable cause the student pilot's inadequate compensation for the existing crosswind conditions and failure to maintain directional control during the touch-and-go takeoff. A factor was his improper use of (failure to reduce) the throttle and normal brakes during the accident sequence. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - on ground/water, takeoff - roll/run - compensation for wind conditions - inadequate, pilot in command (cause) - weather condition - crosswind - directional control - not maintained, pilot in command (cause) - ground loop/swerve - On ground/water collision with object, takeoff - roll/run - object - hangar/airport building - object - sign ## Analysis While attempting to do a touch-and-go takeoff with a 60-degree right 10-knot crosswind, the student pilot advanced the throttle to the full forward position, lost directional control of the airplane, and it veered off the runway and struck a runway sign and a hangar. He made unsuccessful attempts to correct the airplane's direction of travel and stop the airplane with brakes. The student pilot stated that as the airplane was veering off the runway it was at or near flying speed and he concentrated on trying to steer the airplane back on course. The student pilot did not attempt to abort the takeoff. A FAA inspector examined the airplane and noted no mechanical deficiencies with the directional controls, braking, or engine power control systems. ## Factual narrative On February 20, 2003, about 1720 mountain standard time, a Cessna 172S, N3550X, collided with a hangar while attempting to do a touch-and-go takeoff from runway 21 at the Scottsdale Airport (SDL), Scottsdale, Arizona. Arizona Flight Works operated the rental airplane under the provisions of 14 CFR Part 91. The airplane sustained substantial damage. The student pilot, the sole occupant, received serious injuries. Visual meteorological conditions prevailed for the local area instructional flight, and no flight plan had been filed. The flight departed SDL about 1635, and was scheduled to terminate at SDL. In the pilot's written statement he stated that he had flown 45 minutes in the practice area, and was returning to SDL to perform touch-and-go takeoffs and landings. He contacted SDL tower and received a clearance to perform "touch-and-gos" on runway 21. After landing, he applied full throttle to takeoff; however, the airplane veered abruptly to the left. The student pilot indicated that the airplane's airspeed was "close to, or at, flying speed." He stated that he continued to apply pressure to the right rudder to offset the airplane's leftward direction, with no response. He stated that his attempts to compensate for the airplane's direction of travel were unsuccessful. The airplane struck a runway sign and then a hangar. The pilot did not indicate that he reduced the throttle or attempted to do a takeoff abort at any time during the accident sequence. A Federal Aviation Administration (FAA) inspector interviewed the certified flight instructor (CFI) who stated that the student had about 40 hours of total flight time, and it was the student's third solo flight. The CFI further reported that the day of the accident he had flown the accident airplane with no mechanical anomalies encountered. The FAA inspector examined the airplane and noted no mechanical deficiencies with the airframe directional control, braking, or engine power control systems. ## Aircraft - Registration: [N3550X](https://openairdocs.org/deregistered/N3550X-2012-11-08), registration cancelled 2012-11-08, S/N 172S8894 (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: 172S8894 - Airframe hours: 777.9 - Engines: Lycoming IO-360-L2A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Arizona Flight Works - Registered owner: Steve Dahlgren - Airworthiness certificate: Standard, Normal - Last inspection: Continuous airworthiness, January 31, 2003, 36.6 hours before - Departed: SDL, SCOTTSDALE, AZ - Destination: SDL - Airport: SDL, Scottsdale, runway 21, 8,249 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Student pilot; age 38; injuries: serious; student; medical: class 3, valid medical--no waivers/lim.; seat: left; flight hours: 53 total, 53 in this make and model, 3 as pilot in command, 2 in the last 90 days, 2 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 270° at 10 knots, gusting 16 - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 66 °F, dew point 37 °F - Altimeter: 29.75 inHg - Observed at: SDL ## 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 20030220002969A](https://openairdocs.org/incident/20030220002969A), Feb 20, 2003: Cessna 172S, Scottsdale, AZ, Substantial damage. (.19) On February 20, 2003, at 1715 mountain standard time, a Cessna 172S, N3550X, collided with a hangar while attempting to do a touch-and-go takeoff from… 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.