Aviation Accident Summaries

Aviation Accident Summary NYC00FA092

HYANNIS, MA, USA

Aircraft #1

N814M

Dassault DA-900

Analysis

Prior to departure, the flight crew confirmed that the 'windy, rainy and stormy' weather would move out of New York and proceed northeast up into the Hyannis area. Arriving in the Hyannis Airport area, at night, the crew received the ATIS, which stated that winds were from 040 degrees at 20 knots, gusts to 33 knots. The ILS Runway 15 approach was in use. Braking action was reported poor by a Cessna 402, and all surfaces were covered with a patchy thin layer of snow and ice. The PIC determined that the tailwind component for the ILS Runway 15 approach would have exceeded the airplane's limitations, and requested the ILS Runway 24 approach. The airplane touched down about 2,640 feet beyond the approach end of the 5,425-foot long runway. The airplane impacted the localizer antenna, departed the end of the runway, went through a chain link fence, crossed a two-lane road, struck three vehicles on the road, continued into a parking lot, and impacted concrete barriers and two parked vehicles. Examination of the airplane revealed a takeoff and landing card (TOLD) on the instrument panel. Written on the card was the landing distance calculated as 3,050 feet and a notation of 'BA POOR'. At the time of the accident the runway was covered with a 1/2-inch accumulation of ice and snow. According to the Dassault DA-900 Airplane Flight Manual (AFM) Limitations Section, the maximum allowable tailwind component at landing was 10 knots. According to the DA-900 Performance Manual, the maximum safe crosswind on icy runways was 5 knots. The manual also stated, 'For icy runway conditions, landing distance is 3 times the landing distance on dry runway.' Using the factor of 3 and a 10 knot tailwind, a landing distance was computed to be about 10,800 feet. No factors were published for a 20 knot tailwind.

Factual Information

HISTORY OF FLIGHT On March 17, 2000, about 1802 Eastern Standard Time, a Dassault DA-900, N814M, operated by BP Amoco Corporation, was substantially damaged when it overran the runway while landing at Barnstable Municipal-Boardman/Polando Field (HYA), Hyannis, Massachusetts. The two certificated airline transport pilots and two passengers were not injured. Two occupants of vehicles on a public road received minor injures. Instrument meteorological conditions prevailed, and an instrument flight rules flight plan was filed for the executive/corporate flight that originated from the La Guardia Airport (LGA), Flushing, New York. The flight was conducted under 14 CFR Part 91. According to the pilot-in-command (PIC), the VOR Runway 6 approach to HYA had been briefed prior to departing LGA. Arriving in the Hyannis area, the crew received the ATIS "Mike", issued at 1650, which stated that winds were from 040 degrees true at 20 knots, gusts to 33 knots, 1/2 statute mile visibility, snow and freezing fog. Cloud conditions were 900 feet broken, 1,400 feet broken, and 2,000 feet overcast. The ILS Runway 15 approach was in use. The crew determined that the visibility for the VOR Runway 6 approach was below minimums, and the PIC determined that the tailwind component for the ILS Runway 15 approach would have exceeded the airplane's limitations. The PIC requested the ILS Runway 24 approach, and the airplane was then vectored to, and cleared for that approach. During an interview, the PIC stated that he made the decision during the approach that he would land the airplane if the braking action was reported as fair, and discontinue the approach if it was reported as poor. The PIC further stated that the airplane was configured to land, and that he flew the glideslope to the runway. After touchdown, he applied maximum reverse thrust and braking, and called for the "air brakes." As the airplane continued down the runway, he noticed an acceleration, and a lack of braking effectiveness. However, he decided not to attempt a go-around, but opted to "rid[e] it out to the end." A Federal Aviation Administration (FAA) inspector, who arrived at the airport shortly after the accident, stated that the airplane departed the end of the runway, slid through the Runway 24 localizer antenna array and a chain link fence. With a 200-foot section of the chain link fence attached to the number two engine pylon, the airplane crossed a two-lane road and struck three vehicles that were traveling on the road. The airplane continued into a parking lot, and impacted four concrete parking barriers. It then impacted three cement parking lot light fixture bases and two parked vehicles, before coming to a stop. During the overrun, the airplane's left and right wing fuel tanks ruptured. The Massachusetts Department of Environmental Protection estimated that approximately 1,200 gallons of Jet-A fuel spilled from the airplane after it came to a stop. A witness, who was standing outside of the airport operations building, stated that he had an unobstructed view of Runway 24 when he observed the accident airplane approach the runway. The witness estimated that the airplane touched down at a point 2,500 beyond the approach end. The airplane continued another 1,500 feet until the thrust reverser was deployed. As the airplane passed the operations building, the speed was excessive for the remaining runway. The witness then realized that the airplane was not going to stop on the airport property and proceeded to a rescue vehicle. The FAA inspector and a representative from the Commonwealth of Massachusetts Aeronautics Commission examined Runway 24 after the accident. They observed one set of tire tracks in the snow on the runway that correlated to the ground track of the accident airplane. The tire tracks began about 2,640 feet from the approach end of the runway, which was about 2,785 feet from the departure end. According to the passenger seated in the main cabin of the airplane, he could see snow outside the window and it was extremely windy, as the airplane passed though 3,000 feet in it's decent to HYA. As the airplane passed through 1,500 feet, he could see the ground continuously and the airplane was "fighting" to stay level. The airplane was at a very steep angle of decent until touchdown. As the airplane was landing, he could see snow covering the runway and the airplane was not decelerating. The passenger did not recall where the airplane touched down on the runway, or if he had heard the thrust reversers or seen the wing spoilers. The passenger did recall that there was a heavy exhaust noise after the landing. A pilot, who was flying a Piper PA-31 the night of the accident, stated that he had flown from HYA about 1715, and returned to the airport area around 1745. He recalled that the weather conditions were, winds from 070 degrees at 28 knots and gusting. The visibility was about 2 1/2 miles, with an indefinite ceiling. The decision was made to land on Runway 6. After landing, the airplane was turned off of the runway at taxiway Bravo due to the high winds slowing the airplane down after landing. The pilot did not recall if he made a braking action report to the tower, but estimated the conditions as poor, due to the depth of snow and ice on the runway. Excerpts of the cockpit voice recorder (CVR) transcript revealed the following: At the beginning of the transcribed recording, HYA ATIS weather information "Mike" was repeated three times on the CAM (cockpit area mike) and the co-pilot's channel. At 1732:42, the ATIS recording stated, "Hyannis tower information Mike two one five zero weather. the wind zero four zero at two zero gusting three three. visibility one half mile with snow and freezing fog. ceiling's broken at nine hundred broken at one thousand four hundred overcast at two thousand. temperature minus one. dew point minus two. altimeter two niner niner seven. ILS approach runway one five's in use. departing traffic runway six. bird activity on and in the vicinity of the airport. clearance delivery frequency's out of service utilize ground. breaking action is re- reported poor by a Cessna four oh two. all s- surfaces are covered with a patchy thin layer of snow and ice. there are delays to Boston and La Guardia. advise on initial contact. you have Mike." At 1749:36, the pilot stated, "I don't know if you get time to check with the tower to see what the winds are right now. I wouldn't want to get a surprise after we set up on the..." At 1749:43, the co-pilot stated, "Okay." At 1749:45, the pilot stated, "...on the approach you know and have the winds right down the." At 1750:01, the co-pilot stated on the radio, "yes sir we-re gonna be with you in just a second. Could you give me your current winds please." At 1750:11, the tower controller stated, "wind ah zero one zero at ah two five." At 1750:16, the co-pilot stated on the radio, "zero one zero at two five. How's that runway now?" At 1750:22, the tower controller stated, "ah no one's ah landed ah. the last braking action report I received was at ah two zero four one * zulu ah braking action was reported poor by a Cessna four oh two. It's ah looks like it appear to be a little more snow on the runway now." At 1750:43, the co-pilot stated, "all right he said ah the winds are zero one zero at twenty five now. braking action was ah." At 1750:50, the pilot stated, "that's not gonna work. that's a big tailwind on landing." At 1750:54, the pilot stated, "two four would almost work better wouldn't it?" At 1751:11, the pilot stated, "we're gonna have to go around to two four@. I mean I-I that's less tailwind component on two four then would you agree?" At 1751:18, the co-pilot stated, "yeah # you know. one five. you're gonna just..." At 1751:22, the pilot stated, "okay which*..." At 1751:23, the co-pilot stated, "...go over the airport? but see that's you*." At 1751:25, the pilot stated, "...yeah why don't you go ahead and ask ah approach to set us up with that please." At 1751:29, the co-pilot stated, "two four? okay." At 1751:31, the pilot stated, "I don't see how we can do it w-with that much tailwind on landing." The co- pilot replied, "okay." At 1751:38, the co-pilot stated on the radio, "yes sir I wonder if you'd set us up with the ILS to runway two four ah it looks like the winds ah not in our favor on runway one five." At 1751:46, the approach controller stated, "eight one four Mike roger turn right zero niner zero vectors ILS two four final approach course." At 1751:54, the co-pilot stated, "I'll get you set up in one second." The pilot responded, "okay." At 1752:02, the pilot stated, "that sound like the right thing to do to you." At 1752:04, the co-pilot stated, "yeah * your right it's you know I was hoping for a little better but i guess it's not going to work is it." At 1752:12, the co-pilot stated, "I'm gonna get back with it in just a second. I'm gonna get the ah." The pilot responded, "okay." At 1752:33, the pilot stated, "I'd say that's a little less than ten knots of ah tailwind on on landing." At 1754:22, the co-pilot stated, "standby one second I'm gonna get you some." At 1754:31, the co-pilot stated on the radio, "okay we didn't like the winds. we're gonna switch around to the ILS to runway two four. What have you got for braking action and winds now?" At 1754:40, the tower controller stated, "the wind ah zero two zero at two six gusts to three four...ah no braking action reports ah received for runway ah two four." At 1754:57, the copilot stated, "okay he's got zero two zero. # that's gonna be a direct tailwind right there on runway." At 1755:02, the pilot stated, "what what'd he call it now?" At 1755:04, the co-pilot stated, "he's calling it zero two zero." The pilot responded, "okaay." At 1755:08, the co-pilot stated, "see that's gonna be a direct tailwind." At 1755:09, the pilot stated, "we're lan-landing on runway two four right?" At 1755:11, the co-pilot stated, "yeah but see that's that's not good right? cause this is gonna be more of a tailwind there." At 1755:18, the co-pilot stated on the radio, "and for eight one four Mike. Say again the ah the wind." At 1755:24, the tower controller stated, "wind zero two zero at two six gusts to three four." At 1755:29, the co-pilot stated, "zero two zero at two six and see that's more of a tailwind." At 1755:32, the pilot stated, "I don't know@. it looks like it's if you look at one five it..." At 1755:36, the co-pilot stated, "zero two zero." At 1755:37, the pilot stated, "...I understand. zero t-. it's almost a-a direct tailwind. I got twenty five hundred for fifteen hundred. The co-pilot responded, "okay." At 1755:49, the pilot stated, "slow it up here. do you wanna try to figure the component real quick?" At 1755:54, the co-pilot stated, "#. I don't even know where the box is." At 1756:09, the pilot stated, "just look at the compass rose there. it's not a direct tailwind." At 1756:12, the co-pilot stated, "yeah but. okay well. zero two...at well that's got a component there." At 1756:19, the pilot stated, "it's got I know it's got a tailwind component." At 1756:22, the co-pilot stated, "okay one five." At 1756:23, the pilot stated, "...but I'm guessing it's less than ten." At 1757:22, the co-pilot stated, "ah two six one well. yeah you got ninety degrees little bit more***." At 1757:44, the co-pilot stated, "all right @ I think you're right." At 1757:45, the pilot stated, "then okay arm the approach for me." At 1758:37, the tower controller stated, "Falcon eight one four Mike Hyannis tower. runway two four clear to land. ah last braking action report received was by a vehicle ah braking action was reported fair." At 1758:46, the co-pilot stated, "eight one four Mike and your wind right now please." At 1758:52, the tower controller stated, "wind ah zero one zero at two two." At 1758:56, the co-pilot stated, "zero one zero at two two. eight one four Mike." At 1758:57, the pilot stated, "that's got to be less than ten knots. okay." At 1758:58, the co-pilot stated, "all right I'll buy that." At 1800:01, the co-pilot stated, "I got a ground speed of about hundred and fifty nine..." At 1800:04, the pilot stated, "okay thank you." At 1800:44, the co-pilot stated, "okay ground speed's one sixty." At 1800:48, the pilot stated, "okay." At 1801:14, the co-pilot stated, "I don't like it." About 4 seconds later, the CVR recording revealed a sound similar to touchdown, followed by the captain calling for the "auto-brakes." At 1801:32, the CVR recorded a sound similar to several impacts. In a written statement, the first officer revealed that he and the captain reviewed weather information during a lunch break. The weather supported information that he had seen on the Weather Channel and information that was obtained from a satellite weather service. The flight crew then confirmed that the "windy, rainy and stormy" weather would move out of New York and proceed northeast up the Atlantic coast, into the HYA and Boston areas. The first officer also stated he had discussed with the accident flight's captain, a weather situation on a previous flight that was similar to what was occurring the day of the accident. On that flight, which was from Dallas, Texas to HYA, a decision was made to land in Providence, Rhode Island, rather than HYA, due to the stormy conditions. The captain replied to the first officer, "...we should not inconvenience our passenger because of our problems." The captain then asked what the driving time would be from Providence, Rhode Island, to HYA. The accident occurred during the hours of darkness, approximately 41 degrees, 40 minutes north latitude, and 70 degrees, 16 minutes west longitude. FLIGHT CREW INFORMATION Captain The captain held an airline transport certificate with a rating for airplane multi-engine land, and commercial privileges for airplane single engine land. In addition, the captain was type rated in the Dassault DA-50, Lear Jet, Gulfstream G-IV, Cessna CE-650, and Cessna CE-500. The captain reported his total flying experience in airplanes was 13,200 hours. He also reported that he had accumulated about 380 hours in the Dassault DA-900, of which about 63 hours were in the last 90 days. The captain's most recent FAA first class medical certificate was issued on December 17, 1999. The captain received his initial Dassault DA-900 training between February 22 and March 11, 1999. The course was taught by Flight Safety, Teterboro Learning Center, Teterboro, New Jersey. According to a representative of the operator, he recalled that the captain's last attended CRM training course was about 1986. According to company records, the captain had flown a Dassault DA-900 a total of 88.4 hours in the last 90 days, and 2.2 hours in the last 60 days. First Officer The first officer held an airline transport certificate with a rating for airplane multi-engine land. The first officer also held a commercial certificate with privileges for airplane single engine land, and rotorcraft. In addition, the first officer was type rated in the Dassault DA-50, Cessna CE-500, Gulfstream G-1159, Gulfstream G-IV, Sikorsky SK-61, and Boeing BV-107. The first officer reported his total flying experience in all aircraft was 8,760 hours. He also reported that he had accumulated a total of 80 hours in make and model, of which 73 were in the last 90 days. The first officer received his initial Dassault DA-900 training between November 29 and December 16, 1999. The course was taught by Flight Safety, Teterboro Learning Center, Teterboro, New Jersey. The first officer's most recent FAA first class medical certificate was issued on November 19, 1999. According to a representative of the operator, he recalled that the first officer's last attended CRM training course was about 1986. METEOROLOGICAL INFORMATION The weather recorded at HYA, at 1756 was, winds from 020 degrees true at 21 knots, gusts to 34 knots; visibility 3/4 statute mile, li

Probable Cause and Findings

The flightcrew's inadequate coordination and improper weather evaluation. Also causal was the captain's improper decision to continue the approach to a runway with insufficient length and his failure to obtain the proper touch down point on the runway. Factors in the accident were the tailwind conditions and the ice and snow-covered runway.

 

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