Zone

Crash of a Cessna 560 Citation V Ultra in Gainesville

Date & Time: Jun 6, 2016 at 2317 LT
Operator:
Registration:
N145KK
Flight Type:
Survivors:
Yes
Schedule:
Boston – Gainesville
MSN:
560-0276
YOM:
1994
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Following an uneventful flight from Boston-Logan, the crew initiated the descent to Gainesville Airport. Weather conditions at destination were considered as marginal due to the presence over the area of the tropical storm 'Colin'. After landing on a wet runway, the aircraft rolled for about 1,000 feet then veered off runway to the left. While contacting soft ground, the left main gear and the nose gear collapsed then the aircraft came to rest in a grassy area. All three occupants evacuated safely and the aircraft was damaged beyond repair.
Probable cause:
No investigations were conducted by the NTSB on the event.

Crash of a Piper PA-46-350P Malibu Mirage in Zephyrhills: 3 killed

Date & Time: Oct 23, 2009 at 2017 LT
Registration:
N98ZZ
Flight Type:
Survivors:
No
Schedule:
Gainesville – Lakeland
MSN:
46-36169
YOM:
1998
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
2750
Captain / Total hours on type:
110.00
Aircraft flight hours:
1893
Circumstances:
The pilot fueled the airplane prior to departure and flew uneventfully for approximately 30 minutes. The airplane then descended to 2,000 feet on approach to the destination airport, during night visual meteorological conditions. About 30 seconds after being cleared for a visual approach, the pilot declared an emergency to air traffic control and requested assistance to the nearest airport. The controller provided a vector to divert and distance to the nearest suitable airport. The pilot subsequently reported "engine out, engine out" and the airplane impacted wooded terrain about 4 miles northeast of runway 22 at the alternate airport. A post crash fire consumed a majority of the wreckage. Examination of the wreckage, including teardown examination of the engine, did not reveal any preimpact mechanical malfunctions; however, the fuel system and ignition system were consumed by post crash fire and could not be tested.
Probable cause:
A total loss of engine power during a night approach for undetermined reasons.
Final Report:

Crash of a Partenavia P.68C in Gainesville: 3 killed

Date & Time: Nov 7, 2008 at 0246 LT
Type of aircraft:
Operator:
Registration:
N681KW
Flight Type:
Survivors:
No
Schedule:
Key West - Gainesville
MSN:
273
YOM:
1983
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8300
Captain / Total hours on type:
1500.00
Aircraft flight hours:
6971
Circumstances:
The pilot of the multiengine airplane was flying two passengers at night on an instrument-flight-rules flight plan. One of the passengers had been on an organ recipient waiting list and his wife was accompanying him. A viable matched organ was available at a distant hospital and the passenger had to arrive on short notice for surgery the following morning. All radio communications during the flight between the pilot and air traffic control (ATC), a flight service station (FSS), and a fixed-based operator (FBO) were routine. The pilot was aware of the weather at the destination airport, and had commented to ATC about 75 miles from the destination that the weather was "going up and down…like a real thin fog layer.” Additionally, better weather conditions prevailed at nearby suitable airports. The pilot mentioned one of those airports to ATC in the event he decided to divert. According to an employee at an FBO located at the destination airport, the pilot contacted him via radio and asked about the current weather conditions. The employee replied that the visibility was low due to fog and that he could not see the terminal lights from the FBO. The pilot then asked which of the two alternate airports was closer and the employee stated that he did not know. The employee then heard the pilot “click” the runway lights and contact the local FSS. about 5 miles from runway 29, just prior to the initial approach fix, the pilot radioed on the common traffic advisory frequency and reported a 5-mile final leg for runway 29. The FSS reported that the current weather was automated showing an indefinite ceiling of 100 feet vertical visibility and 1/4 mile visibility in fog. The pilota cknowledged the weather information. The weather was below the minimum published requirements for the instrument-landing-system (ILS) approach at the destination airport. Radar data showed that the flight intercepted and tracked the localizer, then intercepted the glideslope about 1 minute later. There were a few radar targets without altitude data due to intermittent Mode C transponder returns. The last recorded radar target with altitude indicated the airplane was at 600 feet, on glideslope and heading for the approach; however, the three subsequent and final targets did not show altitude information. The last recorded radar target was about 1.4 miles from the runway threshold. The airplane flew below glideslope and impacted 100-foot-tall trees about 4,150 feet from the runway 29 threshold. On-ground facility checks and a postaccident flight check of the ILS runway 29 approach conducted by the Federal Aviation Administration did not reveal malfunctions with the ILS. The cabin and cockpit area, including the NAV/COMM/APP, equipment were consumed by a postimpact fire which precluded viable component testing. Detailed examination of the wreckage that was not consumed by fire did not reveal preimpact mechanical malfunctions that may have contributed to the accident. Given that the pilot was aware of the weather conditions before and during the approach, it is possible that the pilot’s goal of expeditiously transporting a patient to a hospital for an organ transplant may have affected his decision to initiate and continue an instrument approach while the weather conditions were below the published minimum requirements for the approach.
Probable cause:
The pilot's failure to maintain the proper glidepath during an instrument-landing-system (ILS) approach. Contributing to the accident were the pilot's decision to initiate the ILS approach with weather below the published minimums, and the pilot's self-induced pressure to expeditiously transport an organ recipient to a hospital.
Final Report:

Crash of a Beechcraft B60 Duke in Gainesville: 3 killed

Date & Time: Apr 16, 2006 at 1153 LT
Type of aircraft:
Operator:
Registration:
N999DE
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Gainesville - Gainesville
MSN:
P-447
YOM:
1978
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
1500
Aircraft flight hours:
2901
Circumstances:
The airplane crashed into the terminal building following a loss of control on takeoff initial climb from runway 25. Witnesses reported that shortly after takeoff, the airplane banked sharply to the left, then it seemed to momentarily stabilize and commence a climb before beginning to roll to the left again. The airplane rolled to an inverted position, entered a dive, collided with the airport terminal building and exploded on impact. The entire airplane sustained severe fire and impact damage. Examination of the engines and propellers revealed no evidence of any discrepancies that would preclude normal operation. All the propeller blades displayed signatures indicative of high rotational energy at the time of impact, indicating that both propellers were rotating, not feathered, and the engines were operating at high power at the time of impact. Components of the autopilot system, specifically the pitch servo assembly and a portion of the roll servo assembly, were identified in the wreckage. The portion of the roll servo assembly found remained attached to a piece of skin torn from the airframe and consisted of the mounting bracket for the roll servo with the capstan bolted to the bracket, clearly indicating that this component had been reinstalled and strongly suggesting that the pilot reinstalled/reactivated all of the removed autopilot components the day before the accident. Maintenance personnel started an annual inspection on the airplane the month prior to the accident and found an autopilot installed in the airplane without the proper paperwork. The pilot explained to them that he designed and built the autopilot and was in the process of getting the proper paperwork for the installation of the system in his airplane. During the inspection, a mechanic found the aileron cable rubbing on the autopilot's roll servo capstan so the mechanic removed the roll servo along with the capstan. Additionally, mechanics disabled the autopilot's pitch servo and removed the autopilot control head. They were in the process of completing the inspection when the pilot asked for the airplane stating that he needed it for a trip. The pilot also asked that the airplane be returned to him without the interior installed. Two days before the accident, the airplane was returned to the pilot with the annual inspection incomplete. The autopilot control head, roll servo and capstan were returned to the pilot in a cardboard box on this date. A friend of the pilot reported that the day before the accident, the pilot completed reinstalling the seats and "other things" in order to fly the airplane the next day. It is possible that improper installation or malfunction of the autopilot resulted in the loss of control; however, the extent of damage and fragmentation of the entire airplane wreckage precluded detailed examination of the flight control and autopilot systems and hence a conclusive determination of the reason for the loss of control.
Probable cause:
The loss of control for an undetermined reason.
Final Report:

Crash of a Cessna 411A in Gainesville

Date & Time: Jan 12, 1984 at 1830 LT
Type of aircraft:
Registration:
N4500Q
Flight Type:
Survivors:
Yes
Schedule:
Conroe - Gainesville
MSN:
411-0300
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
The aircraft crashed while on an ILS approach to the Gainsville Airport. Investigation revealed that the pilot had advised approach control that he was 'low on fuel.' After two missed approaches the pilot radioed that he was 'out of fuel.' The pilot did not have charts or approach plates aboard the aircraft, however ATC was not aware of this factor. Attempts to acquire additional information from the pilot have been unsuccessful. All three occupants escaped with minor injuries.
Probable cause:
Occurrence #1: loss of engine power(total) - nonmechanical
Phase of operation: approach - faf/outer marker to threshold (IFR)
Findings
1. (f) fluid,fuel - exhaustion
2. (c) preflight planning/preparation - improper - pilot in command
3. (c) fuel system - inadequate - pilot in command
4. (c) in-flight planning/decision - improper - pilot in command
----------
Occurrence #2: forced landing
Phase of operation: landing - flare/touchdown
Final Report:

Crash of a Beechcraft E18 in Gainesville: 3 killed

Date & Time: Oct 24, 1980 at 0947 LT
Type of aircraft:
Registration:
N65V
Survivors:
No
Schedule:
Barstow - Lake City
MSN:
BA-144
YOM:
1956
Crew on board:
1
Crew fatalities:
Pax on board:
2
Pax fatalities:
Other fatalities:
Total fatalities:
3
Captain / Total flying hours:
8267
Circumstances:
En route from Barstow to Lake City, the pilot informed ATC about the failure of the right engine and was cleared to divert to Gainesville Airport. On final, in a limited visibility due to fog, the twin engine airplane collided with electronic towers and crashed in a field, bursting into flames. All three occupants were killed.
Probable cause:
Powerplant failure for undetermined reasons. The following contributing factors were reported:
- The pilot failed to see and avoid objects or obstructions,
- Inadequate maintenance and inspection of aircraft on part of the maintenance personnel,
- Fuel system: filters, strainers, screens - missing,
- Low ceiling,
- Fog,
- Complete failure of the right engine,
- Visibility two miles or less,
- Right fuel filter filtering element missing,
- Left filter sub amt of debris,
- Main oil screens abnormally dirty.
Final Report:

Crash of a Beechcraft E18S in Gainesville

Date & Time: Sep 9, 1980 at 2322 LT
Type of aircraft:
Registration:
N43L
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
BA-228
YOM:
1957
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
During the takeoff roll, the twin engine airplane went out of control, veered off runway and eventually collided with few others parked aircraft on the apron, bursting into flames. Both occupants were seriously injured and the aircraft was destroyed. The following aircraft were substantially damaged in the ground accident: a Grumman G-21 Goose registered N33S, a Cessna 206 registered N9423G and a Beechcraft registered N9473D.
Probable cause:
Ground loop and subsequent collision with parked aircraft after the pilot failed to maintain directional control. The following contributing factors were reported:
- Inadequate preflight preparation,
- Improperly loaded aircraft.
Final Report:

Crash of a Cessna 401B in Gainesville

Date & Time: May 12, 1980 at 1936 LT
Type of aircraft:
Registration:
N7931Q
Survivors:
Yes
Schedule:
Jacksonville - Gainesville
MSN:
401B-0031
YOM:
1969
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
5000
Captain / Total hours on type:
3.00
Circumstances:
On final approach to Gainesville Airport, both engines failed simultaneously. The airplane lost height, struck trees and crashed in high vegetation. Both occupants were seriously injured.
Probable cause:
Double engine failure on final approach due to inadequate preflight preparation. The following contributing factors were reported:
- Lack of familiarity with aircraft,
- Mismanagement of fuel,
- Inattentive to fuel supply,
- Fuel starvation,
- Fuel selector positioned between tanks,
- High vegetation,
_ Complete failure of both engines,
- Forced landing off airport on land,
- Auxiliary fuel tanks and left main empty,
- Right main fuel tank 10-15 gallons,
- Left engine fuel selector on left main tank,
- Right engine fuel selector between left main and right auxiliary tank.
Final Report:

Crash of a Beechcraft D18S in Gainesville: 10 killed

Date & Time: Feb 3, 1964 at 0800 LT
Type of aircraft:
Operator:
Registration:
N2999
Flight Phase:
Survivors:
No
Schedule:
Ocala-Gainesville-Jacksonville-Tallahassee
MSN:
A-0811
YOM:
1952
Flight number:
SCA510
Crew on board:
1
Crew fatalities:
Pax on board:
9
Pax fatalities:
Other fatalities:
Total fatalities:
10
Captain / Total flying hours:
16647
Captain / Total hours on type:
486.00
Circumstances:
Shortly after takeoff from runway 06 at Gainesville Airport, while climbing to a height of 200 feet, the twin engine aircraft adopted a nose up attitude then stalled and crashed in a huge explosion about 80 feet past the runway end. The aircraft was destroyed by impact forces and a post crash fire and all 10 occupants were killed.
Probable cause:
The aircraft was improperly loaded and the CofG was out of the enveloppe and too far aft, causing the aircraft to stall after takeoff. Inadequate preflight preparation and/or planning on part of the pilot.
Final Report: