Cessna 560 Citation V
Safety Rating
9.7/10Total Incidents
9
Total Fatalities
24
Incident History
Sav Aviation LLC
A Cessna 560 Citation V, N560RT, landed with at least one gear-up on runway 31 at KRBD.
Chen Aircrafts
The pilot departed on an instrument flight rules flight into instrument meteorological conditions (IMC). Radar data indicated that the airplane entered a left turn after takeoff, consistent with the pilot's instrument clearance. As the airplane climbed to an altitude about 2,410 ft above ground level, its rate of climb increased from about 3,500 ft per minute to 9,600 ft per minute, the stick shaker activated, and the airplane decelerated to about 75 knots. The airplane then entered a descending right turn and rolled inverted before impacting terrain about 1 mile from the airport. All major components of the airplane were located at the accident site, and examination of the wreckage revealed no anomalies with the airplane that would have precluded normal operation. The weather conditions about the time of the accident included an overcast cloud ceiling about 600 ft above ground level. It is likely that the pilot became spatially disoriented after entering the cloud layer, which resulted in the airplane's high rate of climb, rapid loss of airspeed, and a likely aerodynamic stall. The steep descending right turn, the airplane's roll to an inverted attitude, and the high-energy impact are also consistent with a loss of control due to spatial disorientation.
Can-West Corporate Air Charters
The aircraft departed Edmonton-City Centre Airport in the early morning on a positioning flight to Edmonton-Intl, carrying two pilots. En route, the crew encountered IMC conditions with moderate icing and the deicing systems were activated. For unknown reasons, the aircraft landed hard on runway 02, causing the right main gear to collapse. The aircraft veered off runway to the right and came to rest in a grassy area. Both pilots escaped with minor injuries and the aircraft was damaged beyond repair.
Goship Air
Air traffic control cleared the flightcrew for the instrument landing system (ILS) approach to runway 24, which was 4,897 feet long. The flightcrew then reported that they had the runway in sight, cancelled their instrument flight rules (IFR) clearance, and executed a visual flight rules (VFR) approach in VFR conditions to the airport. The reported winds favored a landing toward the east, onto the opposite runway (runway 6). During the approach, after a query from the first officer, the captain indicated to the first officer that he was going to "...land to the east," consistent with the reported winds. However, the final approach and subsequent landing were made to runway 24, which produced a six-knot tailwind. During the approach sequence the captain maintained an airspeed that was approximately 30 knots higher than the correct airspeed for the aircraft's weight, resulting in the aircraft touching down about 1,500 feet further down the runway than normal, and much faster than normal. The captain then delayed the initiation of a go-around until the first officer asked if they were going around. Although the aircraft lifted off the runway surface prior to departing the paved overrun during the delayed go-around it impacted a localizer antenna platform, whose highest non-frangible structure was located approximately 304 feet past the end of the runway, and approximately two feet lower than the terrain at the departure end of the runway. The aircraft continued airborne as it flew over downsloping terrain for about 400 more feet before colliding with the terrain and a commercial storage building that was located at an elevation approximately 80 feet lower than the terrain at the end of the runway. The localizer antenna platform was located outside of the designated runway safety area, and met all applicable FAA siting requirements. The captain had type 2 diabetes, for which he took oral medication and monitored blood sugar levels. He did not reveal his history of diabetes to the FAA. The captain's post-accident toxicology testing was consistent with an elevated average blood sugar level over the previous several months; however, no medical records of the captain's treatment were available, and the investigation could not determine if the captain's diabetes or treatment were potentially factors in the accident. The captain of the accident flight was the sole owner of a corporation that was asked by the two owners of the accident airplane to manage the airplane for them under a Part 91 business flight operation. The two owners were not pilots and had no professional aviation experience, but they desired to be flown to major domestic airports so that they could transfer and travel internationally via commercial airlines. One of the two owners stated that the purpose of the accident flight was to fly a businessman to a meeting, and to also transport one of the owner's wives to visit family at the same destination. According to one of the owners, the businessman was interested in being a third owner in the accident airplane, so the owner permitted the businessman to fly. The owner also stated that the accident pilot told him that the passenger would pay for expenses directly related to the operation of the airplane for the flight (permitted under FAA Part 91 rules), and an "hourly fee" (prohibited under FAA Part 91 rules); however, no documentation was found to corroborate this statement for the accident flight or previous flights.
Circuit City Stores
On February 16, 2005, about 0913 mountain standard time, a Cessna Citation 560, N500AT, operated by Martinair, Inc., for Circuit City Stores, Inc., crashed about 4 nautical miles east of Pueblo Memorial Airport, Pueblo, Colorado, while on an instrument landing system approach to runway 26R. The two pilots and six passengers on board were killed, and the airplane was destroyed by impact forces and post crash fire. The flight was operating under the provisions of 14 Code of Federal Regulations Part 91 on an instrument flight rules flight plan. Instrument meteorological conditions prevailed at the time of the accident.
NetJets
After a visual approach to the 3,975 foot long by 50-foot wide runway, the turbojet airplane touched down about 2,100 feet beyond the landing threshold, and overran the departure end of the runway. The 5,600 hour pilot in command (PIC) reported that the approach speed and descent rate were "normal," and the aircraft was on short final over the trees at the "desired speed." Once the trees were clear, the aircraft descended to the runway at idle power. During the descent the PIC noticed a 16-knot increase in speed above reference. The PIC elected to continue "because the aircraft was close to the runway" and the PIC thought he had "extra landing distance to work with beyond what was required." The PIC reported that the aircraft "floated beyond the desired touchdown point," and "at this point [the pilots were] committed to stopping the aircraft." Passing the last third of the runway, the aircraft turned to the right "without" input from the pilots, overran the departure end, and collided with trees. Once the aircraft left the runway, the PIC stowed the thrust reversers and attempted to shut down the engines. Due to the "violent ride," the PIC managed to shut down one engine. A post-impact fire consumed the aircraft after the crew assisted to evacuate the occupants. No mechanical or maintenance anomalies were discovered with the aircraft. According to the flight manual, based on 29.74 inches HG, 1,808 PA, 30 degrees Celsius, zero wind, and an aircraft landing weight of 14, 500 lbs, the calculated total stopping distance (air and ground distance) at reference speed (Vref), was estimated at 2,955 feet. According to the flight manual, the "total distance" is based on full flaps, speed brakes after touchdown, Vref at 50 feet over the runway threshold, idle thrust when crossing the threshold, and no thrust reverse.
Eagle Air - Switzerland
At 19:43:49 UTC the crew of EAB 220 called clearance delivery (CLD) for the first time and asked if their flight plan to Bern-Belp was available. The answer was in the affirmative and the CLD air traffic controller informed the crew that they would need authorisation for the landing in Bern-Belp. Once it had been clarified that this authorisation had been obtained, EAB 220 called back a little later. CLD informed the pilots that their departure was planned from runway 34. However, they would have to expect a delay at that time, as arrivals and departures were being handled in batches. EAB 220 was scheduled in the next batch for take-off. CLD intimated to the crew an approximate departure time of 20:30 UTC. When the crew called back at 20:13:49 UTC to ask for any news, CLD informed them that departure would now take place in about 45 minutes. Since visual conditions were deteriorating due to the thickening fog, air traffic control had to increase the separation between arriving aircraft. As a result, flight EAB 220’s estimated departure time was delayed to about 21:00 UTC. At 20:24:38 UTC CLD transmitted to the crew a departure clearance. Flight EAB 220 was assigned the standard instrument departure (SID) “WILLISAU 3N” and transponder code 1403. In addition, a departure time of 21:07 UTC was estimated. The CEO of Eagle Air Ltd. had applied in Bern-Belp for a special authorisation for a late landing after 21:00 UTC and obtained a slot until 21:30 UTC at the latest. Since the departure of HB-VLV in Zurich was being further and further delayed, the crew found themselves under increasing time pressure. The crew were in contact with the CEO several times; at the time, the latter was performing the function of the dispatcher. In order to ensure the arrival of HB-VLV in Bern-Belp by 21:30 UTC at the latest, he also telephoned the duty manager in Zurich control tower and urged him several times for an earlier departure time. After a frequency change to apron control, the apron controller cleared EAB 220 to start its engines at 20:43:50 UTC. Approximately at the same time, an airport manager observed that HB-VLV’s right-hand engine was running, although only one pilot was present in the cockpit. He was sitting in the right-hand seat. The other crew member, probably the commander, was using a scraper to remove ice deposits from the left wing. The eye witness later observed how this crew member occupied the left-hand position in the cockpit, shortly before taxiing. Since the pilots were eager to leave their stand in the General Aviation Centre (GAC) Sector 1 as quickly as possible, they were cleared to taxi as far as the holding point for runway 28 just 2 minutes later. There they had to wait for a taxiing Saab 2000 to pass in the opposite direction. EAB 220 was then instructed by the apron controller to continue taxiing to the holding point for runway 34 via taxiways ALPHA, INNER and ECHO. One minute after taxi clearance had been given, the crew of EAB 220 again asked for the wording of this clearance: “Swiss Eagle 220, sorry for that, can you say the clearance again?” It must remain open whether HB-VLV had missed the intersection in the direction of the INNER taxiway. It is clear, however, that the apron controller had to intervene shortly afterwards with a correction: “220, continue on taxiway INNER, INNER, and then ECHO to Holding Point 34, Echo 9”. At 20:56:50 UTC flight EAB 220 made contact with Aerodrome Control (ADC) and stated that the aircraft was on Echo 9 just before the start of runway 34. The air traffic controller (ATCO) requested the crew to wait short of runway 34, since approaches were still taking place in the opposite direction on runway 16. At 21:04:51 UTC ADC cleared the aircraft to line up on runway 34. The crew taxied onto runway 34 and – after they had received take-off clearance at 21:05:54 UTC – initiated a rolling take-off by setting take-off power. At this time, meteorological visibility was 100 m with partial fog. Since the left-hand engine was run up within six seconds to 102 percent of take-off power and the right-hand engine to 58 percent, for a few seconds during the acceleration phase the aircraft veered on the runway to such an extent that it’s heading changed 10 degrees to the right. The crew were only able to bring the aircraft back into alignment with the runway by making a major nose-wheel control correction and by distinctly reducing the thrust of the left-hand engine. Afterwards the two engines were brought synchronously to take-off power and the take-off continued. Flight EAB 220 lifted off from runway 34 at 21:06:40 UTC. Shortly after take-off, the commander of EAB 220 acknowledged the request to change frequency to departure control. At about the same time various members of the airport fire-fighting services, who were inside and in front of the fire-fighting unit satellite “North” between runways 34 and 32, heard noises and saw visual indications of a low-flying aircraft. Immediately afterwards the noise of a crash and the flash of a fire were noted. At 21:07 UTC the aircraft impacted onto the frozen ground 400 m to the south-east of the end of runway 34 and skidded in a northerly direction, leaving a trail of debris. The main body of the wreck finally came to rest 500 m beyond the site of initial impact on runway 14/32. The rescue services reached the burning wreck after a few minutes. DFDR data revealed that the autopilot was disengaged during the whole flight.
Iowa Packing Company
The airplane was circling to land on runway 22 after executing a VOR/DME approach. The airplane impacted the ground approximately one quarter mile northeast of the runway 22 threshold. The wreckage path covered a distance of approximately 350 feet. Control continuity was established. Airframe, engine and navaid examination revealed no abnormalities. The left wing and horizontal stabilizer leading edges had approximately one-eighth inch of rime ice adhering to their leading edges. Two witnesses reported seeing the airplane rolling from the left to the right. The Eagle River AWOS was not available on a VHF radio frequency, due to radio frequency congestion at the O'Hare International Airport, Chicago, Illinois.
Safety Profile
Reliability
Reliable
This rating is based on historical incident data and may not reflect current operational safety.
