Aviation Accident Summaries

Aviation Accident Summary NYC03FA002

Dexter, ME, USA

Aircraft #1

N57EJ

Cessna 525A

Analysis

The pilot/owner initiated a VFR approach and landing in a Cessna 525A, to a 3,009-foot long runway with a tailwind of about 7 knots. The touchdown was 642 feet past the approach end of the runway. Vref was calculated to be 108 kts; however, data from the EGPWS showed the ground speed was about 137 kts, 9 seconds before touchdown, and at touchdown, the speed was estimated to be about 130 kts. After touchdown, the pilot selected ground flaps, which moved the flaps from 35 degrees to 60 degrees, the spoilers auto-deployed, and the speed brakes were extended. The pilot said that after applying the brakes, he felt the brakes pedals pulsing, and did not think the airplane was slowing. He released the brakes for a few seconds and then reapplied them. Again, he felt the pulsing in the pedals, but the airplane was not slowing as he expected. He released the brakes, reset the flaps to takeoff, and applied power to abort the landing when he was about halfway down the runway. The airplane departed the end of the runway and traveled for about 300 feet. Skid marks revealed the initial touchdown was most like made with brakes applied, and no locked wheel crossover protection. Additional skid marks revealed the airplane became airborne after touchdown, and in the next 750 ft, touched down 3 more times, each subsequent touchdown occurring without the full weight of the airplane on the wheels. Tire marks on the last half of the runway were consistent with brakes applied and anti-skid operative. Using the approved flight manual standards, the airplane would have required 3,155 feet to stop. This was predicated on crossing the threshold at 50 feet, at Vref, and included a ground roll of 1,895 feet. However, the pilot touched down at 642 feet from the threshold, which left sufficient runway for stopping. Using the pilot's touchdown point of 642 feet, the airplane was capable of stopping on the runway with a Vref as high as 120 kts. The approach was unstabilized with 4 aural warnings, including 2 sink rate warnings on final approach, the last of which occurred with a descent rate of over 1,700 fpm down, 19 seconds prior to touchdown, and about 400 feet above the ground. The last airborne GPS position was about 2,000 ft from runway touchdown. This would have required a flight path angle of about 3.8 degrees to achieve the reported touchdown position.

Factual Information

HISTORY OF FLIGHT On October 7, 2002, at 1017 eastern daylight time, a Cessna 525A, N57EJ, was substantially damage during a runway overrun at the Dexter Regional Airport (1B0), Dexter, Maine. The certificated airline transport pilot and one passenger received serious injuries, and two passengers received minor injuries. Visual meteorological conditions (VMC) prevailed for the business flight that departed Robertson Airport (4B8), Plainville, Connecticut, about 0930. An instrument flight rules (IFR) flight plan was filed and activated, and the flight was conducted under 14 CFR Part 91. According to the pilot, he departed Plainville and climbed to flight level 290. The flight progressed without incident, and when the airplane was approximately 80 miles south of Dexter, the pilot initiated a descent. While being vectored for the GPS runway 34 approach, and descending through 6,000 feet mean sea level (MSL), the airplane entered VMC. Once clear of the clouds, flight visibility was approximately 10 miles. The pilot cancelled his IFR clearance when the airplane was about 10 miles south of the airport, and proceeded under visual flight rules (VFR). The pilot further stated: "...touchdown accomplished within first 1/4 of runway...throttles in idle before touchdown, flaps in landing position. At touchdown, flaps to ground position (spoilers deployed), apply brakes, pedal pressure was firm, felt sensation of anti-skid pulsing. Aircraft did not decelerate noticeably. Released brakes to allow reset. Reapplied brakes, no difference. Commenced go-around. Throttles full forward, ground flaps to take-off position...This was the last I remember until regaining consciousness. I tried to shut engines down, couldn't get levers to idle cut-off...." The pilot added that he left the cockpit and went to the tail cone baggage compartment where he disconnected the battery. He returned to the cockpit and brought the throttles to idle cut-off, after which the engines stopped. In a follow-up interview, the pilot reported that about half way down the runway, he became concerned about stopping within the distance remaining, so he aborted the landing. With approximately 1,500 feet remaining, he removed his feet from the brake pedals, advanced the power levers to takeoff, and raised the flaps two notches to the takeoff position. The airplane, continued down the runway, but did not accelerate as expected. The pilot's memory regarding the aborted landing and subsequent impact was fragmented. He remembered the airplane departing the far end of the runway, and then impacting the ground, but he could not recall the airspeed when he overran the runway, or if he reapplied the brakes after aborting the landing. The pilot added that the winds reported by approach control favored runway 16. He chose to land on runway 34 because the tailwind component was negligible, and to land on runway 16 would require a steeper approach due to a hill north of the runway. The pilot further stated that the enhanced ground proximity warning system (EGPWS) sounded "Sink Rate," while on final. He added it was not unusual for him to get the "Sink Rate" warning, and that the system had sounded in the past even when the airplane was descending on a visual glidepath at 500 fpm. The accident occurred during the hours of daylight. The wreckage was located at 45 degrees, 00.50 minutes north latitude, 69 degrees, 14.45 minutes west longitude, and an elevation of approximately 530 feet msl. PERSONNEL INFORMATION The pilot held an airline transport pilot certificate with an airplane multi-engine land rating, and type ratings in the CE-500, CE-525, and CE-525S (single pilot authorization). He also held a private pilot certificate with an airplane single engine land rating. He was last issued a Federal Aviation Administration (FAA) first-class airman medical certificate on January 25, 2001. The pilot's total flight experience was 2,450 hours, which included 763 hours in the Cessna CE-525, and 126 hours in the Cessna CE-525A. According to records from Flight Safety Inc, in Wichita, Kansas, the pilot had last attended Cessna 525 recurrent training from November 26 through November 28, 2001. This included ground school and three simulator periods. A check of available records revealed no adverse comments. AIRCRAFT INFORMATION The type certificate designation for the airplane was 525A. Cessna Aircraft Company referred to the airplane as the CJ-2. The airplane was approved for single pilot operations. The trailing edge flaps were controlled by a variable position selector, with two detents, up, and 15 degrees for approach. In addition, the flap lever could be set to the landing position, which extends the flaps to 35 degrees. At the landing stop, if the flap lever was lifted, it could be moved further aft to extend the wing flaps to 60 degrees on the ground. A weight and balance was prepared by Cessna Aircraft Company, and revealed that the center of gravity of the airplane at takeoff and landing were outside of the aft limit of the weight and balance envelope. The landing weight was estimated to be 10,852 pounds, and center of gravity was 0.8 inches aft of the aft limit. The pilot submitted an alternate weight summary that showed a landing weight of 10,202. The weight summary differed from that calculated by the original investigative team. The revised weight summary was within the center of gravity envelope at landing. The EGPWS maintained a continuous recording of specified parameters. When a cockpit aural warning was activated, the preceding 10 seconds of data, along with the next 20 seconds of data was stored, and was available for recall. The captured data was stored at one-second intervals, using elapsed timing. In addition, each time the landing gear squat switches transitioned from ground to air, or air to ground, the elapsed time, latitude and longitude, the airplane heading, and GPS altitude were recorded. The airplane was equipped with Williams International FJ44-2C engines. The flight idle rpm was 65 percent N2, and the ground idle was 54 percent N2. There was a 8 second delay after initial touchdown before the engines would retard to ground idle. Wind information was displayed on the primary flight display in the form of an arrow, which pointed in the direction the wind was blowing relative to the nose of the airplane, and the velocity was displayed in knots. METEOROLOGICAL INFORMATION There was no recorded weather at Dexter. The pilot was given Bangor winds of 220 degrees at 6 knots, (observation taken at 0955), when he made contact with Bangor approach control. The 0955 weather observations at Bangor, and other area airports indicated the winds were from the southeast to the southwest at 6 to 9 knots, including gusts to 15 knots. AIRPORT INFORMATION Dexter was an uncontrolled airport with a single runway 16/34. The published airport elevation was 533 feet. The asphalt surface runway was 3,009 feet long, 80 feet wide. There were no visual aids for a pilot to use in determining a glide path to the runway. The airport was constructed on top of a hill. No obstructions were listed for runway 16; however, several nearby obstructions were listed for the approach to runway 34. Lower terrain prevailed to the south for over 2 miles. Lower terrain prevailed to the north for about a mile. Further north, there was rising terrain about 150 feet above airport elevation within 2 miles of the departure end of the runway. A peak elevation of 840 feet was located 2 miles from the approach end of runway 16. FLIGHT RECORDERS The airplane was not equipped with, nor required to be equipped with a flight data recorder (FDR), or cockpit voice recorder (CVR). RADAR AND OTHER REMOTELY RECORDED DATA Radar data was obtained from Bangor Approach Control. The airplane was identified by its assigned transponder code of 4607. The airplane was last observed at 1015:52.03, about 6,000 feet from the approach end of runway 34, on a heading of 340 degrees, and a recorded altitude of 1,000 feet mean sea level (MSL), plus or minus 50 feet. WRECKAGE AND IMPACT INFORMATION Examination of the landing runway revealed five distinct sets of skid marks; initial touchdown, three additional touchdowns on the runway, and the final set of skid marks as the airplane departed the runway. The first set of skid marks started at 642 feet from the approach end of the runway, and were consistent with a left main landing gear touchdown first. The right wheel touched the runway about 30 feet further down the runway. Both marks were similar, starting with a narrow skid from the center of the tire, which widened to full tire width. After skidding for over 10 feet on the full width of the tire, the skid marks stopped abruptly. Following the skid marks, a series of rubber marks, estimated to about 1 foot in length were observed. These marks were estimated to be separated by the length of one tire rotation. These marks were consistent with rubber stamping on the runway as the tires rolled after having been heated during the initial touchdown skid. The repeating marks were progressively lighter with each revolution of the tire. The second set of skid marks started about 250 feet from the initial touchdown on the runway, 892 feet from the approach end of the runway. The left wheel skid started with a narrow strip of rubber, and then got lighter. The skid then transitioned from a narrow skid to a wider tire skid in about 2 feet, continued for about 6 feet, and stopped. The skid was visible again, with the same tire width as before. The right wheel showed a much lighter mark. The skid marks were consistent with the airplane touching down on the runway. The third set of skid marks started about 500 feet from the initial touchdown on the runway, and 1,142 feet from the approach end of the runway. Both the right and left tire skid marks started as a narrow band and increased in width as they progressed. The skid marks were more pronounced on the left wheel than the right wheel. The left wheel skid was partially interrupted as the tire passed over a transverse runway repair. The variable width of the skid marks were consistent with an airplane that did not have a constant weight on its wheels. In addition, the skid marks were also consistent with the airplane touching down on the runway. The fourth set of skid marks started about 750 feet from the initial touchdown, and 1,392 feet from the approach end of the runway. The left wheel skid mark started as a narrow band and increased in width, and then decreased in width, followed by rubber stamping. The mark was consistent with a tire touching down. The right tire mark was not clearly defined. After the fourth set of skid marks, continuous tire marks were visible. The marks indicated some retardation of tire rotation, but not enough to cause a skid. These marks were consistent with brakes applied, and anti-skid functioning. The fifth set of skid marks started about 50 feet prior to the departure end of the runway. Intermittent skid marks were visible from both tires as the skid marks angled to the right. After departing the runway, the airplane entered a grass overrun. Initially, the grass was laid over and torn from the ground, then the marks transitioned to grass that was laid over, but not torn from the ground. In the overrun, a third tire mark, equal distance between the two main landing gear tire marks was also visible. The tire marks continued to a drop-off that was located at the end of the overrun and 179 feet past the departure end of the runway. The drop-off was elevated above a dirt road that ran perpendicular to the runway, and was approximately 10 feet lower in elevation. Running along the north side of the road was a pipeline. The pipeline was approximately 12 inches in diameter, and scratch marks were visible on the top of the casing, aligned with the direction of travel of the airplane, and in line with airplane and ground marks identified as tire marks from the airplane. The airplane came to rest beyond the road, on a magnetic heading of 360 degrees, approximately 300 feet past the departure end of the runway. The airplane was intact, and all the structural and flight control surfaces were present. Damage to the airplane consisted of impact damage to the nose, left wing, bottom of the tail section, and right wing. The nose landing gear was crushed rearward, both main landing gear were extended, and the left main landing gear was bent rearward, partially separated from its mounts. Both main landing gear tires were in serviceable condition and inflated. The pre-impact condition of the nose wheel tire could not be confirmed. The left and right flaps were approximately 15 degrees. The cockpit was intact, but deformed. The flap handle was up, along with the flap indicator. The thrust attenuators were stowed, and the control switch was in the AUTO position. The anti-skid control switch was ON. The power brake accumulator was discharged, and the brake fluid reservoir was full. The parking brake was off, the gear and brake emergency pneumatic accumulator was charged, and the emergency brake handle was stowed. TESTS AND RESEARCH Seats and Shoulder Harnesses The two cockpit seats were forwarded to Pacific Scientific in Yorba Linda, California, for further examination under the supervision of an FAA inspector. On the right seat, the shoulder harness would not extend more than 24 inches. The tamper seal on the inertia reel was found to be broken, and the anti-rebound spring positioned 180 degrees out of alignment. When properly repositioned, the shoulder harness extended for its full length of 47 inches. The shoulder harness reel was also found to lock when subjected to the "no lock" test where it is extended at 0.75 G acceleration force. No problems were noted on the left seat. There was no record of any work on the seats entered in the airplane maintenance records to document when the inertia reel had been worked on. Airplane Re-Examination - June 2003 The airplane was re-examined on June 13, 2003, by an air safety investigator from Cessna Aircraft Company. Five bit fault indicators had been installed on the forward baggage compartment side of the forward pressure bulkhead. Three were found tripped; including the left-hand transducer, the right-hand transducer, and the squat switch disagree fault indicators. The Cessna investigator further reported that the squat switch disagree could cause a loss of touchdown protection if there was a disagreement between the two main landing gear squat switches for a period of 12 seconds or longer. This information was not displayed on the annunciator panel. Airplane Brakes - January 2004 On January 27, 2004, the brakes were examined for wear at Telford Aviation, Bangor, Maine, under the supervision of an FAA inspector. Brake wear was determined by measuring extension of the pins when the brake system had been pressurized. According to the Goodrich brake overhaul manual, when the extension on either pin on a wheel brake was 0.325 inches or less, the manual called for the brakes to be overhauled. The minimum extension on the left wheel brake was 0.8050 inches. The minimum extension on the right wheel brake was 0.8185 inches. Crane Aerospace - February 2004 On February 17, 2004, anti-skid components manufactured by Crane Aerospace were examined at their facility in Burbank, California, under the supervision of an FAA inspector. No problems were noted with these units. Cessna Aircraft Company - March 2004 On March 2, 2004, components from the braking system that were manufactured by the Cessna Aircraft Company were examined at their facility in Wichita, Kansas, under the supervision of an FAA inspector. No problems were noted with these units. Crane Aerospace - March 2004 On March 18, 2004, the anti-skid computer was examined under the supervision of an FAA inspector, at the Crane Aerospace facility in Wichita, Kansas. No problems were noted with the unit. Service Bulletins Cessna had released five service bulletins for the 525A

Probable Cause and Findings

was the pilot's improper decision to land with excessive speed, and his delayed decision to perform an aborted landing, both of which resulted in a runway overrun. A factor was the tail wind.

 

Source: NTSB Aviation Accident Database

Get all the details on your iPhone or iPad with:

Aviation Accidents App

In-Depth Access to Aviation Accident Reports