# NTSB LAX05LA223: Piper PA-28-180, N9254J, Yuma, AZ, July 2, 2005 - Type: NTSB accident investigation - Classification: Accident · No injuries · Limited investigation · Final report - Date: July 2, 2005, 11:30 local (18:30 UTC) - Place: Yuma, AZ - Coordinates: 32.656387, -114.605834 - Nearby events: https://openairdocs.org/map.md?lat=32.6564&lon=-114.6058&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: No injuries - Injuries: 4 uninjured - Status: Completed, report April 25, 2006 - Report: Approved by Office Director - Parties: Federal Aviation Administration - NTSB case key (mKey): 61894 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=LAX05LA223 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/61894/pdf - Page: https://openairdocs.org/ntsb/LAX05LA223 ## Probable cause the pilot's misjudged distance and altitude, which resulted in an undershoot and collision with a airport boundary fence short of the runway. A factor in the accident was the pilot's lack of familiarity flying the airplane at a high gross weight with a center of gravity near the forward limit, which would have affected the elevator control forces and the amount of nose up elevator available. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Undershoot, approach - vfr pattern - final approach - lack of experience, pilot in command (contributing factor) - aircraft weight and balance - high, pilot in command (contributing factor) - distance/altitude - misjudged, pilot in command (cause) - In flight collision with object, approach - vfr pattern - final approach - object - fence ## Analysis The airplane collided with an airport perimeter fence short of the runway during landing and nosed over. While on final approach with the flaps fully extended and the throttle at 1,700 rpm, the airplane began descending rapidly. The pilot retracted the flaps 10 degrees and applied full power. The airplane continued to descend until it struck the airport perimeter fence and nosed over. The pilot reported that this was his first flight with three passengers on board the airplane. Weight and balance calculations showed that upon takeoff, the airplane exceeded its forward center of gravity limit by 1 inch and the gross weight was 2,347.42 pounds. During landing, the calculated center of gravity was near its forward limit, but 0.3 inches within the weight and balance envelope. The gross weight during landing was 2,257.42 pounds. The maximum gross weight for the airplane was 2,400 pounds. ## Factual narrative On July 2, 2005, at 1130 mountain standard time, a Piper PA-28-180, N9254J, collided with an airport perimeter fence during landing and nosed over at Yuma International Airport, Yuma, Arizona. Yuma Flying Club was operating the privately registered airplane under the provisions of 14 CFR Part 91. The private pilot and three passengers were not injured; the airplane sustained substantial damage. Visual meteorological conditions prevailed. The airplane departed Yuma for a local area personal flight about 1030, and no flight plan had been filed. According to the pilot, he had taken his friends on a local flight. On final approach with the flaps fully extended, and the throttle at 1,700 revolutions per minute (rpm), the airplane began descending rapidly. The pilot retracted the flaps 10 degrees and applied full power. He could not recall if the engine responded. The airplane continued to descend until it struck the airport perimeter fence and nosed over. The pilot reported that this was his first flight with three passengers on board the airplane. He received his private pilot certificate on April 16, 2005, and had about 95 hours total flight time. The pilot did not report any mechanical problems with the airplane prior to departure. According to the airport manager, approximately 35 gallons of fuel were drained from the airplane following the accident. The National Transporation Safety Board investigator performed weight and balance calculations for the flight using the pilot operating handbook (POH) for the airplane. Upon takeoff, the calculated gross weight was 2,347.42 pounds with an arm of 90.5 inches aft of the datum. Comparing the calculations with a center of gravity (CG) and weight chart showed that the airplane exceeded its forward CG range by approximately 1 inch. During landing, the calculated gross weight of the airplane was 2,257.42 pounds with an arm of 90.3 inches aft of the datum. Comparison of these calculations with the CG and weight chart showed the airplane loaded near its forward CG limit, but approximately 0.3 inches within the weight and balance envelope. The maximum gross weight for the airplane was 2,400 pounds. According to the Pilot's Handbook of Aeronautical Knowledge (AC 61-23C), "The forward center of gravity limit is often established at a location which is determined by the landing characteristics of the airplane. It may be possible to maintain stable and safe cruising flight if the CG is located ahead of the prescribed forward limit; but during landing which is one of the most critical phases of flight, exceeding the forward CG limit may cause problems. Manufacturers purposely place the forward CG limit as far rearward as possible to aid pilots in avoiding damage to the airplane when landing." In addition, AC 61-23C states, "A restricted forward center of gravity limit is also specified to assure that sufficient elevator deflection is available at minimum airspeed. When structural limitations or large stick forces do not limit the forward CG position, it is located at the position where full-up elevator is required to obtain a high angle of attack for landing." The engine was test-run at Air Transport, Phoenix, Arizona, on July 25 under the auspices of the Federal Aviation Administration coordinator. The engine was operationally tested to 2,400 rpm and idled at 700 to 800 rpm. The magneto check produced a 100-rpm drop on the right and a 75-rpm drop on the left. No operational anomalies were noted. When compared with the Champion Aviation Check- A- Plug chart AV-27, the spark plug coloration for the number 1 cylinder was consistent with a slightly rich operation; the coloration of the remaining spark plugs was consistent with normal operation. ## Aircraft - Registration: [N9254J](https://openairdocs.org/deregistered/N9254J-2012-09-06), registration cancelled 2012-09-06, S/N 28-3329, built 1966 (OpenAirDocs) - Reported make and model: Piper PA-28-180 - Registry model: [Piper PA-28-180](https://openairdocs.org/model/piper-pa-28-180) (registry code 7102808) (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: 28-3329 - Airframe hours: 3333.7 - Engines: Lycoming O-360-A3A 180 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Registered owner: Yuma Flying Club - Airworthiness certificate: Standard, Normal - Last inspection: Annual, November 1, 2004, 207.4 hours before - Departed: YUM, Yuma, AZ - Destination: YUM - Airport: YUM, Yuma International Airport, runway 8, 6,146 × 150 ft, concrete ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 39; injuries: none; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; seat: left; flight hours: 95 total, 95 in this make and model, 20 in the last 90 days, 5 in the last 30 days ## Weather - Conditions: Visual (VMC), Day - Wind: 170° at 10 knots - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 100 °F, dew point 54 °F - Altimeter: 29.79 inHg - Observed at: YUM ## 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 20050702015849A](https://openairdocs.org/incident/20050702015849A), Jul 2, 2005: Piper PA28180, Yuma, AZ, Destroyed. (-23) While on short final for landing, aircraft landed short of runway on airport access road and ran through closed gate in airport perimeter fence. Both… 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.