# NTSB LAX05LA160: Cessna 172RG, N4970V, Grand Canyon, AZ, May 7, 2005 - Type: NTSB accident investigation - Classification: Accident · Minor injuries · Limited investigation · Final report - Date: May 7, 2005, 16:37 local (23:37 UTC) - Place: Grand Canyon, AZ - Coordinates: 35.95222, -112.146667 - Nearby events: https://openairdocs.org/map.md?lat=35.9522&lon=-112.1467&mi=10 - Phase of flight: [Initial climb](https://openairdocs.org/ntsb-phases/350) (OpenAirDocs' grouping) - Highest injury: Minor injuries - Injuries: 3 minor - Status: Completed, report February 28, 2006 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 61443 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX05LA160 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61443/pdf - Page: https://openairdocs.org/ntsb/LAX05LA160 ## Probable cause the pilot-in-command's failure to properly lean the mixture, which resulted in a power deficiency, a degraded climb capability, and the inability to attain/maintain an adequate airspeed that led to a stall/mush condition while departing during high density altitude conditions. Also causal, was the pilot-in-command's inaccurate preflight performance and weight and balance calculations. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of control - in flight, takeoff - initial climb - weather condition - high density altitude - mixture - incorrect, pilot in command (cause) - aircraft performance,climb capability - exceeded - aircraft weight and balance - exceeded, pilot in command (cause) - airspeed - not obtained/maintained, pilot in command (cause) - stall/mush - encountered, pilot in command (cause) - In flight collision with terrain/water, descent - uncontrolled - terrain condition - ground ## Analysis During an attempted takeoff, the airplane settled back to the ground and impacted a field about 1 mile south of the airport. The pilot reported that prior to the flight he performed performance calculations for the airplane to ensure that it was capable of departing the higher altitude airport. Performance calculations indicated that with the gross weight near the specified maximum, the airplane would need about 4,500 feet to take off. Prior to departure, the pilot configured the airplane with the flaps retracted and the mixture control in the full forward (rich) position. The Safety Board calculated gross weight of the airplane was 2,767 pounds (117 pounds over the airplane's maximum certified gross weight of 2,650 pounds). The pilot reported that his instructor told him to use an airplane empty weight of 1,624 pounds in his calculations, which the instructor said was typical for the airplane type and could be used for this specific airplane. Using this weight, the airplane would still have been 47 pounds in excess of the maximum gross weight. Performance calculations using the Pilot Operating Handbook (POH) for the airplane indicated a ground roll of 3,118 feet (zero wind 3,464 feet) and the distance to clear a 50- foot obstacle was 3,741 feet (zero wind 4,157 feet) with a predicted 327 feet per minute rate of climb. The POH notes that prior to takeoff from fields above 3,000 feet elevation, the mixture should be leaned to give maximum power in a full throttle, static run-up. The runway the pilot attempted to depart from was 8,999 feet in length with an elevation of 6,609 feet mean sea level (msl). The density altitude was calculated to be 7,728 feet msl. Following the accident, the spark plugs were removed and were black and sooty, an indication that the engine was running rich. The engine was then test-run with no operational anomalies noted. ## Factual narrative HISTORY OF FLIGHT On May 7, 2005, at 1637 mountain standard time, a Cessna 172RG, N4970V, settled back to the ground during an attempted takeoff from the Grand Canyon National Park Airport, Grand Canyon, Arizona. The accident location is in a field about 1 mile south of the airport. Grey Eagle Aviation, Inc., the registered owner of the airplane, was operating it under the provisions of 14 CFR Part 91. The private pilot and two passengers sustained minor injuries; the airplane sustained substantial damage. Visual meteorological conditions prevailed and a visual flight rules flight plan was filed but not yet activated. The flight was destined for Palomar Airport, Carlsbad, California, and was originating at the time of the accident. The pilot had flown the airplane to the Grand Canyon from Carlsbad earlier that day. According to witnesses, the airplane was departing runway 21. When the main gear lifted from the runway's surface, the airplane flew in ground effect but did not climb. It proceeded down the runway without climbing prior to settling to the ground in a field. During the ground impact, the left wing collapsed downward at its root and the airplane nosed down. During a telephone conversation with the pilot a few days following the accident, the pilot reported that the airplane would not climb during takeoff. After the airplane left the runway's surface, he retracted the landing gear in an attempt to increase the climb rate. The airplane settled toward the ground. The pilot attempted to land on the remaining runway and extended the gear. By the time the gear was extended, there was not enough usable runway to land the airplane. He then maneuvered the airplane to avoid trees and force-landed the airplane in the terrain. The mixture was set in the full-rich (forward) position. No control or power anomalies were noted with the airplane on the flight to the Grand Canyon earlier that day. In a written statement submitted to a National Transportation Safety Board investigator on May 13, the pilot and his passengers said they departed Carlsbad without incident. He recalled the tachometer at take off being just over 2,500 revolutions per minute. Once established in the climb at 83 knots, he set 2,500 rpm and 25 inches manifold pressure as he had been instructed during his recent check flight with Grey Eagle Aviation. The takeoff felt normal and the takeoff distance seemed "fairly" normal, possibly a little longer than his previous flights from Carlsbad. The airplane appeared to climb satisfactorily and he had no problems climbing to 10,000 feet. During cruise, there were brief periods with some roughness from the engine. However, the temperatures and pressures all seemed normal during these occasions and the pilot was not concerned over continuation of this flight. The roughness was unaffected by variation of the mixture selected or the altitudes at which he flew. Once established in the cruise he leaned the mixture. When adjusting the mixture and throttle, he was not able to achieve 2,700 rpm and used 2,400 to 2,500 rpm maximum and 20 to 21 inches manifold pressure at cruise. Initially, he did not think too much about the maximum rpm achievable. He later recalled thinking about the decreased performance and the occasional roughness during the flight, and referred to the Pilot's Operating Handbook (POH) a couple of times during the flight to confirm the rpm and manifold pressure values. Prior to his arrival at Grand Canyon Airport, the pilot reconfirmed his takeoff performance calculations because he wanted to know how much fuel to take on. He reviewed his flight guide and again noted the runway length, the airport altitude, and the temperature from the automated terminal information service (ATIS). He referred to the POH takeoff charts using 8,000 feet and 20 degrees Celsius and this suggested the distance to 50 feet would be 4,440 feet, and the predicted rate of climb to be around 400 feet per minute. Performance calculations indicated that with the gross weight near the specified maximum, the airplane would need about 4,500 feet to take off. The pilot further stated that the taxi and run-up just prior to the accident flight were uneventful. As the airplane began gaining speed on runway 21, it lifted from the runway; however, it would not climb. No unusual sounds were noted. The pilot then retracted the landing gear in hopes of attaining a better climb performance. When the landing gear retracted, the airplane sank and would not climb. The pilot then decided to abort the takeoff and extend the landing gear. By the time the landing gear was down-and-locked, there was no usable runway landing surface available. The pilot continued flying the airplane at a low altitude, while altering his course to the left in an effort to prevent impact with trees. The pilot then force landed the airplane in a field. Prior to takeoff, the flaps were retracted and the mixture control was in the full forward (rich) position. The pilot further stated that during his training, he used an airplane weight of 1,624 pounds while completing a weight and balance calculation. He reported that his instructor said that this airplane weight was okay to use and that this was similar to the actual weight of the airplane as given in the weight and balance statement. Because of this understanding, the pilot used the airplane weight of 1,624 pounds on all of his weight and balance calculations for the airplane. The pilot calculated the airplane's takeoff weight to be 2,650.2 pounds using an airplane weight of 1,624 pounds and a baggage weight of 15 pounds. In a later statement sent to the Safety Board investigator on August 23, the pilot reported that the mixture was leaned prior to departure from the airport. After speaking with a Federal Aviation Administration (FAA) inspector regarding a flight assessment test, the pilot thought about the original statement he made regarding the circumstances of the accident. The pilot stated that he moved the engine, propeller, and mixture controls forward following the accident when he was retrieving personal items from the airplane. In his original notes written just after the accident he noted, "Mixture- rich side of lean at T-off [takeoff]", which is why he wrote "rich" in his written report. In this message, the pilot also reported that he had notated, "mixture leaned (in climb)- no significant improvement in ROC [rate of climb]." The pilot reported having 12 hours of flight time operating out of airports above 3,000 feet mean sea level (msl) or above. Following the accident, the pilot underwent 5 hours of dual training at airports over 7,100 msl. The pilot also noted that he may have encountered windshear or turbulence as he retracted the gear during the attempted takeoff. TESTS AND RESEARCH The engine was examined and test-run on June 22, 2005, at Air Transport, Phoenix, Arizona with Safety Board investigator and FAA inspector present. The spark plugs were removed and the electrodes were black and sooty. The engine was manually rotated and thumb compression was obtained on all cylinders, in firing order. A borescope inspection revealed no mechanical deformation on the valves, cylinder walls, or on the internal cylinder heads. The engine was test-run and the magneto check produced a drop of 75 rpm on each magneto. No operational deficiencies were noted. The Safety Board investigator completed weight and balance calculations for the accident flight. Based on weights given by the pilot and responding rescue personnel, the following information was determined: Pilot and Passenger: 445 pounds Rear Passenger: 210 pounds Fuel: 372 pounds Baggage: 45 pounds Aircraft Weight: 1,695 pounds Total Gross Weight: 2,767 pounds with a 44.85 center of gravity. Using the airplane weight of 1,624 pounds, the following weight and balance calculations wer ## Aircraft - Registration: [N4970V](https://openairdocs.org/deregistered/N4970V-2005-12-29), registration cancelled 2005-12-29, S/N 172RG0435, built 1980 (OpenAirDocs) - Reported make and model: Cessna 172RG - Registry model: [Cessna 172RG](https://openairdocs.org/model/cessna-172rg) (registry code 2072438) (OpenAirDocs) - Registry engine: [Lycoming O&VO-360 series](https://openairdocs.org/engine/lycoming-o-vo-360-series) (registry code 41514, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 172RG60435 - Airframe hours: 5716 - Engines: Lycoming O-360-F1A6 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Grey Eagle Aviation, Inc. - Airworthiness certificate: Standard, Normal - Last inspection: 100 hour, March 1, 2005, 64 hours before - Departed: KGCN, Grand Canyon, AZ - Destination: KCRQ, Palomar Airport, CA - Flight plan: VFR - Airport: GCN, Grand Canyon, runway 21, 8,999 × 150 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 40; injuries: minor; private; airplane ratings: single-engine land; medical: class 2, without waivers/limitations; last flight review April 1, 2005; seat: left; flight hours: 206 total, 51 in this make and model, 158 as pilot in command, 10 in the last 90 days, 8 in the last 30 days, 4 in the last 24 hours ## Weather - Conditions: Visual (VMC), Day - Wind: 260° at 9 knots, gusting 15 - Visibility: 10 statute miles - Lowest ceiling: 8,000 ft overcast - Temperature: 54 °F, dew point 30 °F - Altimeter: 30.01 inHg - Observed at: KGCN ## 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 20050507009029A](https://openairdocs.org/incident/20050507009029A), May 7, 2005: Cessna 172RG, Grand Canyon, AZ, Substantial damage. (-23) On may 7, 2005 at approximately 1637 local time (PDT), a Cessna CE-172-RG, N4970V, standard certification experienced a forced landing after take off on… 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.