Air Safety Week Free e-Mail Newsletter Free Aviation Job Alerts
Home Avionics Aviation Maintenance Rotor & Wing Air Safety Week Aircraft Value News Regional Aviation News Very Light Jets
View by Category:  Military | Commercial | Business & General Aviation | Rotorcraft | Air Traffic Control | Maintenance
Advanced Search


Aviation Today Market Leaders
Subscribe
Jobs
Podcasts
Webinars
Videos
Blogs
Databases &
   Buyer's Guides

White Papers/
   Technical Reports/
   Supplements

Research Reports
Article Archives
Press Releases
From the PR Wires
Industry Links

Top Stories
Aviation e-letter
Financial Center
Calendar
Media Kits
About Us
Contact Us

Monday, May 12, 2008

Unusual Cessna 510 Accident

The pilot of a Cessna Citation Mustang that suffered severe mechanical problems in April is lucky to have gotten his stricken aircraft back on the ground. He lost his primary flight display (PFD) and autopilot and fought off fatigue to safely land the aircraft (registration: N54PV) without injury to himself...

For immediate service; more information; and multi-user access (site license), non-profit organization, educational institute pricing, contact Karen Garner kgarner@accessintel.com at (301) 354-1612.


This story is only available to paid subscribers. Please login below with your username and password if you are a subscriber.

Username:
Password:
  What is my password?

Subscribe     Trial

The pilot of a Cessna Citation Mustang that suffered severe mechanical problems in April is lucky to have gotten his stricken aircraft back on the ground.

He lost his primary flight display (PFD) and autopilot and fought off fatigue to safely land the aircraft (registration: N54PV) without injury to himself and three passengers.

The accident occurred April 19, 2008 in Carlsbad, CA with the aircraft sustaining substantial damage following the pilot's intentional ground loop maneuver during the landing roll on Runway 24 at McClellan-Palomar Airport.

The flight departed Lincoln Regional Airport, Lincoln, CA, with a planned destination of Carlsbad. At the time of the accident, the pilot had canceled his instrument flight rules (IFR) flight plan, and was executing a visual flight rules (VFR) approach to Runway 24 in visual meteorological conditions.

The en route cruise was normal as the airplane approached Carlsbad and the pilot began a standard terminal arrival route (STAR); during the initial segment of the STAR the pilot configured the autopilot in vertical speed mode.

The pilot told NTSB investigators that as the airplane crossed over the Avenal transition [waypoint on the SADDE6 STAR] about 30,000 feet msl, the right [co-pilot's] Primary Flight Display (PFD) began to flicker. About five minutes later, as the airplane continued to descend through 28,000 feet msl, the left PFD flashed an alert indicating that the autopilot had disconnected. The pilot immediately felt the disengagement of the autopilot from what he described as the heavy control forces on the control yoke that he had to exert to fly the airplane. He additionally noted that the autopilot activation light was not illuminated, further confirming that the system had disengaged.

Shortly thereafter, the pilot discovered that the electric pitch trim [located on the control yoke] was not operational. After establishing that the pitch trim was not functional, he ultimately began using the trim wheel located on the center consol, which operated normally. The pilot noted that following the autopilot failure, the flight director bars overlaid about a 10-degree pitch up attitude despite the descending flight path.

Flying the airplane by hand, the pilot continued the STAR and reported to air traffic controllers (ATC) that he had an autopilot malfunction. As the pilot descended to 5,000 feet msl, the airplane encountered instrument meteorological conditions (IMC). Controllers vectored the pilot to the instrument landing system-equipped Runway 24.

The airplane broke out of the overcast conditions at 2,600 feet msl and the pilot relayed to controllers that he would make a visual approach to the runway. The pilot noted that he was overwhelmed with the electrical failures and fatigued from maneuvering the airplane by hand for such a long duration (which he approximated was around 45 minutes).

The airplane crossed the runway threshold configured with the wing flaps fully extended [30 degrees] and flying about 15 knots faster than his predetermined landing speed; the pilot had previously calculated a Vref speed of 87 knots. From looking at the airspeed indicator, he noted that the airplane was fast for landing but thought the runway would be long enough to accommodate the likely delayed touchdown. As the airplane progressed down the runway he approached the small uphill slope that was located around the middle. The airplane approached the apex of the sloping runway and the pilot began to clearly distinguish where the runway surface ended, which was sooner than he had anticipated.

The touchdown occurred far down the runway surface, past the middle location. The pilot realized that despite his braking attempts and extension of speed brakes, the airplane was going to continue off the runway surface over a small downsloping cliff at the end. He determined that he would not be able to abort the landing due to the airplane's diminished groundspeed and elected to perform a 180-degree course reversal by rapidly turning the control yoke. The airplane ground looped, coming to rest in a dirt area south of the runway; the main landing gear collapsed and the flaps folded under the wings.


Post a Comment

Name:
Email:
Comments:

Please enter the letters or numbers you see in the image.

 
Your message will be reviewed before it is posted.

Copyright © 2008 Access Intelligence, LLC. All rights reserved. Reproduction in whole or in part
in any form or medium without express written permission of Access Intelligence, LLC is prohibited.