# NTSB LAX06LA108: Cessna 172N, N739GY, Sacramento, CA, February 11, 2006 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 11, 2006, 15:10 local (23:10 UTC) - Place: Sacramento, CA - Coordinates: 38.516666, -121.5 - Nearby events: https://openairdocs.org/map.md?lat=38.5167&lon=-121.5000&mi=10 - Phase of flight: [Taxi](https://openairdocs.org/ntsb-phases/250) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 5 uninjured - Status: Completed, report May 29, 2007 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 63223 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX06LA108 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/63223/pdf - Page: https://openairdocs.org/ntsb/LAX06LA108 ## Probable cause (aircraft 2) the failure of the pilot of the other airplane to maintain an adequate clearance from obstacles while taxiing. ## Probable cause (aircraft 1) the pilot's failure to maintain adequate clearance from obstacles while taxiing. ## 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 - object - aircraft parked/standing - clearance - not maintained, pilot in command (cause) - Collision between aircraft (other than midair), standing - engine(s) operating - object - aircraft parked/standing - clearance - not maintained, pilot of other aircraft (cause) ## Analysis (aircraft 2) A taxiing Cessna 172N collided with this airplane that was stationary in the run-up area. The pilot of the Cessna 172N positioned himself behind this airplane in the run up area. He completed his checklists, and requested takeoff clearance. He received permission to taxi into position and hold on the runway, and added power to taxi around this airplane. He said he failed to realize the close proximity of his airplane's left wing to this airplane's rudder. His airplane's wing tip collided with the this airplane's rudder and vertical stabilizer. ## Analysis (aircraft 1) A taxiing Cessna 172N collided with a stationary Cessna 172P in the run-up area. The pilot of the Cessna 172N positioned himself behind the 172P in the run up area. He completed his checklists, and requested takeoff clearance. He received permission to taxi into position and hold on the runway, and added power to taxi around the 172P. He said he failed to realize the close proximity of his airplane's left wing to the 172P's rudder. His airplane's wing tip collided with the other airplane's rudder and vertical stabilizer. ## Factual narrative (aircraft 2) On February 11, 2006, about 1510 Pacific standard time, a taxiing Cessna 172N, N739GY, collided on the ground with a standing Cessna 172P, N54661, at Sacramento Executive Airport, Sacramento, California. Executive Flyers, Inc., was operating both of the airplanes under the provisions of 14 CFR Part 91. The private pilot and one passenger in the taxiing Cessna 172N were not injured; the airplane sustained minor damage. The certified flight instructor (CFI), the student pilot, and one passenger in the standing Cessna 172P were not injured; the airplane sustained substantial damage. The Cessna 172N was preparing to depart on a local personal flight, and the standing Cessna 172P was departing on a local instructional flight. Visual meteorological conditions prevailed, and no flight plan had been filed for either airplane. The CFI in the 172P stated that he and his student were in the run up area. Their airplane was stationary, and he saw the pilot of the 172N stop behind him. After completing their takeoff checks, they switched from ground control to tower frequency. He heard the 172N pilot ask and receive clearance for takeoff. He saw the 172N move forward, and felt that it was getting too close to his airplane. He was about to move forward when the left wing of the 172N hit his airplane's rudder. The pilot of the Cessna 172N stated that he positioned himself behind the 172P in the run up area. He completed his checklists, and requested takeoff clearance. He received permission to position and hold, and added power to taxi around the 172P. He said that he failed to realize the close proximity of his airplane's left wing to the 172P's rudder. His airplane's wing tip collided with the other airplane's rudder and vertical stabilizer. Both pilots immediately stopped and shut down their engines. ## Factual narrative (aircraft 1) On February 11, 2006, about 1510 Pacific standard time, a taxiing Cessna 172N, N739GY, collided on the ground with a standing Cessna 172P, N54661, at Sacramento Executive Airport, Sacramento, California. Executive Flyers, Inc., was operating both of the airplanes under the provisions of 14 CFR Part 91. The private pilot and one passenger in the taxiing Cessna 172N were not injured; the airplane sustained minor damage. The certified flight instructor (CFI), the student pilot, and one passenger in the standing Cessna 172P were not injured; the airplane sustained substantial damage. The Cessna 172N was preparing to depart on a local personal flight, and the standing Cessna 172P was departing on a local instructional flight. Visual meteorological conditions prevailed, and no flight plan had been filed for either airplane. The CFI in the 172P stated that he and his student were in the run up area. Their airplane was stationary, and he saw the pilot of the 172N stop behind him. After completing their takeoff checks, they switched from ground control to tower frequency. He heard the 172N pilot ask and receive clearance for takeoff. He saw the 172N move forward, and felt that it was getting too close to his airplane. He was about to move forward when the left wing of the 172N hit his airplane's rudder. The pilot of the Cessna 172N stated that he positioned himself behind the 172P in the run up area. He completed his checklists, and requested takeoff clearance. He received permission to position and hold, and added power to taxi around the 172P. He said that he failed to realize the close proximity of his airplane's left wing to the 172P's rudder. His airplane's wing tip collided with the other airplane's rudder and vertical stabilizer. Both pilots immediately stopped and shut down their engines. ## Aircraft 1 - Registration: [N739GY](https://openairdocs.org/aircraft/N739GY), registered now, S/N 17270543, built 1978 (OpenAirDocs) - Reported make and model: Cessna 172N - Registry model: [Cessna 172N](https://openairdocs.org/model/cessna-172n) (registry code 2072434) (OpenAirDocs) - Registry engine: [Lycoming 0-320 series](https://openairdocs.org/engine/lycoming-0-320-series) (registry code 41508, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 17270543 - Airframe hours: 9152 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Minor damage - Flight: Personal, Part 91 - Operator: Executive Flyers, Inc. - Registered owner: Frank Radecki - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, November 1, 2005 - Departed: SAC, Sacramento, CA - Airport: SAC, Sacramento Executive, runway 20, 5,503 × 150 ft, asphalt ## Aircraft 2 - Registration: [N54661](https://openairdocs.org/aircraft/N54661), registered now, S/N 17275028, built 1981 (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: 17275028 - Airframe hours: 11823 - Engines: Lycoming O-320 160 horsepower reciprocating - Damage: Substantial damage - Flight: Instructional, Part 91 - Operator: Executive Flyers, Inc. - Registered owner: Joel Carey - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, February 1, 2006 - Departed: SAC, Sacramento, CA - Airport: SAC, Sacramento Executive, runway 20, 5,503 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N739GY; age 23; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review July 1, 2005; seat: left; flight hours: 166 total, 55 in this make and model, 111 as pilot in command, 9 in the last 90 days, 8 in the last 30 days - Flight instructor, aircraft N54661; age 21; injuries: none; commercial, flight instructor; airplane ratings: single-engine land, multi-engine land; instrument ratings: airplane; medical: class 1, without waivers/limitations; last flight review May 1, 2005; seat: right; flight hours: 1,310 total, 1,000 in this make and model, 1,260 as pilot in command, 200 in the last 90 days, 50 in the last 30 days - Student pilot, aircraft N54661; injuries: none; student; medical: class 3, with waivers/limitations; seat: left; flight hours: 42 total, 8 in this make and model, 10 in the last 90 days, 4 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 310° at 3 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 70 °F, dew point 46 °F - Altimeter: 30.31 inHg - Observed at: SAC ## FAA reports on this event (2) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 20060211003489A](https://openairdocs.org/incident/20060211003489A), Feb 11, 2006: Cessna 172N, Sacramento, CA, Minor damage. (-23) Aircraft taxied into other aircraft in the runup area prior to takeoff. - [Accident 20060211013592A](https://openairdocs.org/incident/20060211013592A), Feb 11, 2006: Cessna 172P, Sacramento, CA, Minor damage. (-23) Aircraft was in runup area at Sacramento exec airport when another aircraft taxied into it, striking the vertical structure. 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.