# NTSB FTW97LA107: Piper PA-32R-300, N4477F, Salida, CO, February 18, 1997 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: February 18, 1997, 14:15 local (21:15 UTC) - Place: Salida, CO - Coordinates: 38.529632, -106.000633 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.5296&lon=-106.0006&mi=10 - Phase of flight: [Takeoff](https://openairdocs.org/ntsb-phases/300) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 5 uninjured - Status: Completed, report August 25, 1997 - Report: Approved by Office Director - NTSB case key (mKey): 20161 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=FTW97LA107 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/20161/pdf - Page: https://openairdocs.org/ntsb/FTW97LA107 ## Probable cause The airplane's performance being exceeded due to the pilot's inadequate preflight planning. Factors were the uphill runway, high density altitude, and the pilot's lack of experience performing takeoffs from a high altitude airport. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Gear collapsed, takeoff - aborted - preflight planning/preparation - inadequate, pilot in command (cause) - performance data - exceeded, pilot in command (cause) - airport facilities,runway/landing area condition - uphill (contributing factor) - weather condition - high density altitude (contributing factor) - lack of experience, pilot in command (contributing factor) ## Analysis The pilot reported that during takeoff roll the aircraft accelerated to 60 MPH like it 'normally' does; however, it took 'longer than normal to accelerate to 80 MPH.' The aircraft appeared to 'lift off fine, but it didn't seem to climb as well as he would have liked.' He put the gear up and about 30 to 35 feet above the runway he lowered the aircraft's nose to accelerate to the best angle of climb airspeed. Instead of accelerating and continuing to climb, the aircraft began to descend. He 'cut the power,' and as the airplane touched down, the nose and left main landing gear collapsed. The airplane has automatic extending landing gear. The pilot did not use any flaps for the takeoff. The pressure altitude at the time of the accident was 7,489 feet and the temperature was 48 degrees Fahrenheit. The performance data derived for these conditions would be off of the chart. In the same section, there is a warning that, 'Performance information derived by extrapolation beyond the limits shown on the charts should not be used for flight planning purposes.' This was the pilot's third takeoff from a high altitude airport. Runway 24 rises 1.9 degrees, which equates to a 117 foot rise. ## Factual narrative On February 18, 1997, at 1415 mountain standard time, a Piper PA-32R-300 airplane, N4477F, registered to and operated by a private owner as a Title 14 CFR Part 91 personal flight, was substantially damaged during an aborted takeoff at Harriet Alexander Field Airport near Salida, Colorado. Visual meteorological conditions prevailed, and a VFR flight plan was filed. The instrument rated private pilot and four passengers were not injured. The flight was originating at the time of the accident. During a telephone interview with the investigator-in-charge the pilot reported that during the takeoff roll on runway 24, the aircraft accelerated to 60 MPH like it "normally" does; however, it took "longer than normal to accelerate to 80 MPH." The aircraft appeared to "lift off fine, but it didn't seem to climb as well as he would have liked." He put the gear up and about 30 to 35 feet above the runway he lowered the aircraft's nose to accelerate to the best angle of climb airspeed of 100 MPH. Instead of accelerating and continuing to climb the aircraft began to descend. He "cut the power," and as the airplane touched down on the runway, the nose landing gear and left main landing gear collapsed. The airplane came to a stop 2,500 feet from the departure end of the runway. The pilot further reported that he did not use any flaps for the takeoff, and he did not remember checking the manifold pressure during run-up or takeoff. He computed the gross weight of the aircraft as 3,502 pounds. The aircraft's maximum gross weight is 3,600 pounds. The pilot also reported that this was his third takeoff from a high altitude airport. The airplane was equipped with a "backup gear extender" system which automatically extends the landing gear. Landing gear extension is designed to occur, even if the selector is in the up position, at airspeeds below approximately 118 MPH with power off. A review of the performance charts in the Piper Aircraft Corporation's flight manual for the PA-32R-300 revealed the following information. In Section 5, titled "Performance," figure 5-9 the "Flaps Up Takeoff Performance" chart shows the performance for takeoff corrected for pressure altitude, temperature, gross weight, and wind. The pressure altitude at the airport at the time of the accident was 7,489 feet, the temperature was 48 degrees Fahrenheit, and density altitude was 8,600 feet. The performance data derived for these conditions would be off of the chart. In the same section, there is a warning that, "Performance information derived by extrapolation beyond the limits shown on the charts should not be used for flight planning purposes." Airport facilities information shows that runway 24 has an uphill grade of 1.9 degrees, which equates to a 117 foot rise. Also, runway 24 is recommended for landing, and runway 06 for departures, weather and traffic permitting. According to the FAA inspector, the firewall, the left wing tip fuel tank, and the left wing spar sustained structural damage. ## Aircraft - Registration: [N4477F](https://openairdocs.org/deregistered/N4477F-2019-03-02), registration cancelled 2019-03-02, S/N 32R-7680449, built 1976 (OpenAirDocs) - Reported make and model: Piper PA-32R-300 - Registry model: [Piper PA-32R-300](https://openairdocs.org/model/piper-pa-32r-300) (registry code 7103213) (OpenAirDocs) - Registry engine: [Lycoming TI0-540 series](https://openairdocs.org/engine/lycoming-ti0-540-series) (registry code 41533, turbo-prop) (OpenAirDocs) - Category: Airplane - Serial number: 32R-7680449 - Airframe hours: 3000 - Engines: Lycoming I0-540-K1G5D 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: James M. Morris - Airworthiness certificate: Standard, Normal - Last inspection: Annual, February 12, 1997, 4 hours before - Departed: 0V2 - Destination: TYR, TYLER, TX - Flight plan: VFR - Airport: 0V2, Harriet Alexander Field, runway 24, 7,350 × 75 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 38; private; airplane ratings: single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: left; flight hours: 423 total, 139 in this make and model, 300 as pilot in command, 12 in the last 90 days, 7 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 240° at 15 knots - Visibility: 20 statute miles - Lowest ceiling: none - Temperature: 48 °F ## 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 19970218001669A](https://openairdocs.org/incident/19970218001669A), Feb 18, 1997: Piper PA32R300, Salida, CO, Substantial damage. On takeoff, insufficient power. Tried to land on runway. Nose gear and left main collapsed on landing. ## Other investigations on N4477F (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 CEN16LA375](https://openairdocs.org/ntsb/CEN16LA375), Sep 19, 2016: Piper PA 32R-300 (N4477F), Grants, NM, destroyed. Probable cause: A loss of engine power for reasons that could not be determined based on the available information. 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.