# NTSB LAX02LA241: Cessna 172P, N97056, Mesa, AZ, July 25, 2002 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 25, 2002, 16:00 local (23:00 UTC) - Place: Mesa, AZ - Coordinates: 33.460834, -111.728332 - Nearby events: https://openairdocs.org/map.md?lat=33.4608&lon=-111.7283&mi=10 - Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 2 uninjured - Status: Completed, report July 29, 2004 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 55319 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX02LA241 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/55319/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=55319 - Page: https://openairdocs.org/ntsb/LAX02LA241 ## Probable cause (aircraft 2) the pilot of the other airplane'ss use of an excessive taxi speed and too close of a spacing interval to the Cessna 152, which resulted in an on-ground collision when the Cessna 152 abruptly stopped. ## Probable cause (aircraft 1) the pilot's use of an excessive taxi speed and too close of a spacing interval to the airplane ahead, which resulted in an on-ground collision when the preceding airplane abruptly stopped. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Collision between aircraft (other than midair), taxi - to takeoff - taxispeed - excessive, pilot in command (cause) - clearance - not maintained, pilot in command (cause) - Collision between aircraft (other than midair), standing - engine(s) operating - taxispeed - excessive, pilot of other aircraft (cause) - clearance - not maintained, pilot of other aircraft (cause) ## Analysis (aircraft 2) The airplane collided with a standing Cessna 152 while taxiing. Before taxiing, the pilot completed a preflight inspection and a brake check, both of which showed no abnormalities with the airplane. He was taxiing at 1,000 rpm, which was about 13 miles per hour. Just before approaching the run up area, he began to reduce the throttle and applied brake pressure. The right brake did not respond. In an effort to avoid a propeller strike, the pilot decided to remain on the taxiway. He applied full left brake pressure and the airplane's left wing tip collided with a C152's vertical stabilizer. The airplane continued to the left and departed the taxiway. The operator stated during recovery the airplane's brakes were tested. Both brakes appeared to be functioning properly. A repair shop that assessed the damage stated that after a thorough inspection, they could not find any malfunction of the braking system. ## Analysis (aircraft 1) The pilot was taxing to the run up area and collided with a Cessna 152 that was standing with engine running in the run up area. Before taxiing, the pilot completed a preflight inspection and a brake check, both of which showed no abnormalities with the airplane. He was taxiing at 1,000 rpm, which was about 13 miles per hour. Just before approaching the run up area, he began to reduce the throttle and applied brake pressure. The right brake did not respond. In an effort to avoid a propeller strike, the pilot decided to remain on the taxiway. He applied full left brake pressure and the airplane's left wing tip collided with this airplane's vertical stabilizer. The airplane continued to the left and departed the taxiway. The operator stated during recovery the airplane's brakes were tested. Both brakes appeared to be functioning properly. A repair shop that assessed the damage stated that after a thorough inspection, they could not find any malfunction of the braking system. ## Factual narrative (aircraft 2) On July 25, 2002, about 1600 mountain standard time, a Cessna 172P, N97056, collided with a standing Cessna 152, N152BR, while taxiing for departure at Falcon Field Airport (FFZ), Mesa, Arizona. Sawyer Aviation Training Center owned and operated both airplanes under the provisions of 14 CFR Part 91. The Cessna 172P received minor damage and the Cessna 152 received substantial damage. Neither the certified flight instructor (CFI) in N97056, nor the student pilot in N152BR was injured. The positioning flight was intending to depart FFZ, with a planned destination of Scottsdale Airport (SDL), Scottsdale, Arizona. Visual meteorological conditions prevailed and a flight plan had not been filed. In a written statement, the CFI, who was piloting the Cessna 172, reported he was attempting to taxi to the run up area for runway 22L. His student was taxiing in the Cessna 152 directly ahead of him, and he was planning to fly behind her en route to SDL. Before taxiing, he completed a preflight inspection and a brake check, both of which showed no abnormalities with the airplane. While taxiing, he had to complete a sharp right turn, which he accomplished by added right brake pressure. He continued taxiing at 1,000 rotations per minute (rpm), which was about 13 miles per hour (mph). Just before approaching the run up area, he began to reduce the throttle and applied brake pressure. The right brake did not respond. In an effort to avoid a propeller strike, the CFI decided to remain on the taxiway. He applied full left brake pressure and the airplane's left wing tip collided with the Cessna 152's vertical stabilizer. The airplane continued to the left and departed the taxiway. During the accident, the Cessna 152 incurred damage to the vertical stabilizer and rudder. During a telephone interview with the National Transportation Safety Board investigator-in-charge (IIC), the operator of both airplanes thought that the CFI was probably taxiing too close behind the student pilot. When the student pilot turned and stopped, the CFI did not have enough time to react and collided with the airplane. The operator stated he talked to a controller in the tower that witnessed the accident. The controller indicated that the airplanes were taxiing within a very close proximity of one another. The operator also stated that Royal Aviation recovered the plane shortly after the accident had occurred. While towing it down the taxiway, they tested the brakes. Both brakes appeared to be functioning properly. He later talked to Arizona Aviation, a repair shop that was assessing the damage. They stated that after a thorough inspection they could not find any malfunction of the braking system. No repairs were made on the braking system. ## Factual narrative (aircraft 1) On July 25, 2002, about 1600 mountain standard time, a Cessna 172P, N97056, collided with a standing Cessna 152, N152BR, while taxiing for departure at Falcon Field Airport (FFZ), Mesa, Arizona. Sawyer Aviation Training Center owned and operated both airplanes under the provisions of 14 CFR Part 91. The Cessna 172P received minor damage and the Cessna 152 received substantial damage. Neither the certified flight instructor (CFI) in N97056, nor the student pilot in N152BR was injured. The positioning flight was intending to depart FFZ, with a planned destination of Scottsdale Airport (SDL), Scottsdale, Arizona. Visual meteorological conditions prevailed and a flight plan had not been filed. In a written statement, the CFI, who was piloting the Cessna 172, reported he was attempting to taxi to the run up area for runway 22L. His student was taxiing in the Cessna 152 directly ahead of him, and he was planning to fly behind her en route to SDL. Before taxiing, he completed a preflight inspection and a brake check, both of which showed no abnormalities with the airplane. While taxiing, he had to complete a sharp right turn, which he accomplished by added right brake pressure. He continued taxiing at 1,000 rotations per minute (rpm), which was about 13 miles per hour (mph). Just before approaching the run up area, he began to reduce the throttle and applied brake pressure. The right brake did not respond. In an effort to avoid a propeller strike, the CFI decided to remain on the taxiway. He applied full left brake pressure and the airplane's left wing tip collided with the Cessna 152's vertical stabilizer. The airplane continued to the left and departed the taxiway. During the accident, the Cessna 152 incurred damage to the vertical stabilizer and rudder. During a telephone interview with the National Transportation Safety Board investigator-in-charge (IIC), the operator of both airplanes thought that the CFI was probably taxiing too close behind the student pilot. When the student pilot turned and stopped, the CFI did not have enough time to react and collided with the airplane. The operator stated he talked to a controller in the tower that witnessed the accident. The controller indicated that the airplanes were taxiing within a very close proximity of one another. The operator also stated that Royal Aviation recovered the plane shortly after the accident had occurred. While towing it down the taxiway, they tested the brakes. Both brakes appeared to be functioning properly. He later talked to Arizona Aviation, a repair shop that was assessing the damage. They stated that after a thorough inspection they could not find any malfunction of the braking system. No repairs were made on the braking system. ## Aircraft 1 - Registration: [N97056](https://openairdocs.org/deregistered/N97056-2013-06-05), registration cancelled 2013-06-05, S/N 17276150, built 1984 (OpenAirDocs) - Reported make and model: Cessna 172P - Registry model: [Cessna 172P](https://openairdocs.org/model/cessna-172p) (registry code 2072436) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172-76150 - Airframe hours: 11701.2 - Engines: Lycoming O-320-DJ2 160 horsepower reciprocating - Damage: Minor damage - Flight: Positioning, Part 91 - Registered owner: Sawyer School of Aviaiton - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, August 2, 2002, 50.6 hours before - Departed: FFZ, Mesa, AZ - Destination: SDL, Scottsdale, AZ - Airport: FFZ, Falcon Field Airport ## Aircraft 2 - Registration: [N152BR](https://openairdocs.org/deregistered/N152BR-2011-03-02), registration cancelled 2011-03-02, S/N 15285232 (OpenAirDocs) - Reported make and model: Cessna 152 - Registry model: [Cessna 152](https://openairdocs.org/model/cessna-152) (registry code 2071835) (OpenAirDocs) - Category: Airplane - Serial number: 15285232 - Engines: Lycoming O-235-L2C 110 hp reciprocating - Damage: Substantial damage - Flight: Positioning, Part 91 - Airworthiness certificate: Standard, Normal - Departed: FFZ, Mesa, AZ - Destination: SDL, Scottsdale, AZ - Airport: FFZ, Falcon Field Airport ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N97056; age 22; injuries: none; commercial, flight instructor; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 1, valid medical--no waivers/lim.; last flight review April 12, 2002; seat: left; flight hours: 599 total, 335 in this make and model, 527 as pilot in command, 179 in the last 90 days, 87 in the last 30 days, 4 in the last 24 hours - Pilot, aircraft N152BR; injuries: none; student; medical: class 1, valid medical--no waivers/lim.; seat: left; flight hours: 65 total ## Weather - Conditions: Visual (VMC), Day - Wind: 250° at 7 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 102 °F, dew point 63 °F - Altimeter: 29.88 inHg - Observed at: SDL, 4 nm away ## Other investigations on N97056 (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. ## Docket (2 files) The files NTSB released with the investigation on June 4, 2004, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=55319. 419 KB in all. - Pilot/Operator Aircraft Accident Report, NTSB Form 6120.1 (item 1, .PDF, 382 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40463836&FileExtension=.PDF&FileName=Pilot%2FOperator%20Aircraft%20Accident%20Report,%20NTSB%20Form%206120.1-Master.PDF - Record of Conversation with H. Miller (item 2, .PDF, 37 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40207642&FileExtension=.PDF&FileName=Record%20of%20Conversation%20with%20H.%20Miller-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.