Zone

Crash of a Piper PA-46-310P Malibu in Port Orange

Date & Time: Feb 2, 2023 at 1200 LT
Registration:
N864JB
Flight Phase:
Flight Type:
Survivors:
Yes
MSN:
46-08009
YOM:
1986
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Circumstances:
Shortly after takeoff from Port Orange-Spruce Creek Airport Runway 23, the single engine airplane encountered difficulties to gain height, impacted trees and crashed on a golf course located south of the airfield. Both occupants were rescued, among them one was slightly injured. The airplane was destroyed.

Crash of an Epic LT in Port Orange: 2 killed

Date & Time: Dec 27, 2016 at 1756 LT
Type of aircraft:
Registration:
N669WR
Flight Type:
Survivors:
No
Site:
Schedule:
Millington – Port Orange
MSN:
029
YOM:
2009
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
4246
Captain / Total hours on type:
956.00
Aircraft flight hours:
822
Circumstances:
The private pilot obtained a full weather briefing before departing on a long cross-country flight. The destination airport was forecast to be under visual meteorological conditions, but there was an AIRMET and Center Weather Advisory (CWA) issued for low instrument flight rules (IFR) conditions later that day. The briefer told the pilot to check the weather again en route to see if the AIRMET and CWA had been updated. At the time the pilot stopped for fuel, another CWA was issued for low IFR conditions at his destination airport; however, there were no records to indicate that the pilot obtained this information during the fuel stop or after departing on the last leg of the flight. A review of air traffic control communications revealed that, about 10 minutes before arriving at the airport, the pilot reported that he had obtained the current weather conditions at his destination airport. The most recent observation, about 1 hour before the accident indicated good visibility; however, the weather reporting equipment did not provide ceiling heights. It is unknown if the pilot obtained weather information from nearby airports, which were reporting low instrument meteorological conditions (visibility between 1/4 and 1/2 mile and ceilings 200-300 ft above ground level [agl]). Additionally, three pilot reports (PIREPs) describing the poor weather conditions were filed within the hour before the accident. The controller did not relay the PIREPs or the CWA information to the pilot, so the pilot was likely unaware of the deteriorating conditions. Based on radar information and statements from witnesses, the pilot's approach to the airport was unstabilized. He descended below the minimum descent altitude of 440 ft, and, after breaking through the fog about 100 ft agl, the airplane reentered the fog and completed a 360° right turn near the approach end of the runway, during which its altitude varied from 100 ft to 300 ft. The airplane then climbed to an altitude about 800 ft before radar contact was lost near the accident site. The airplane came to rest inverted, consistent with one witness's statement that it descended through the clouds in a spin before impact; post accident examination revealed no preimpact anomalies with the airplane or engine that would have precluded normal operation. Although the pilot was instrument rated, his recent instrument experience could not be established. The circumstances of the accident, including the restricted visibility conditions and the pilot's maneuvering of the airplane before the impact, are consistent with a spatial disorientation event. It is likely that the pilot experienced a loss of control due to spatial disorientation, which resulted in an aerodynamic stall and spin.
Probable cause:
The pilot's loss of airplane control due to spatial disorientation, which resulted in the exceedance of the airplane's critical angle of attack and an aerodynamic stall/spin. Contributing to the accident was the pilot's failure to fly a stabilized approach consistent with the published instrument approach procedure.
Final Report:

Crash of a Beechcraft 300 Super King Air in Port Orange

Date & Time: Apr 14, 2004 at 1915 LT
Registration:
N301KS
Flight Type:
Survivors:
Yes
Schedule:
Stuart – Daytona Beach
MSN:
FA-61
YOM:
1985
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
0
Captain / Total flying hours:
3495
Captain / Total hours on type:
147.00
Circumstances:
The pilot stated that he initiated a fuel transfer due to a fuel imbalance. To affect the fuel transfer, he said he "began crossfeed right to left." When the airplane was about 5 to 10 miles away from Spruce Creek Airport, the pilot said he began his descent from 12,500, and also executed a left turn to begin setting up to land, when suddenly, both engines ceased operating. When he leveled the wings both engines restarted due to auto-ignition. He said the fuel gages showed 300 to 350 lbs of fuel for the right tank, and 100 to 150 pounds on the left, so he decided to continue his approach to Spruce Creek Airport. As he approached Spruce Creek Airport, he again entered a left bank to prepare for a left base to runway 23, and while established in the left turn, both engines ceased operating a second time. He said he did not think he could reach the runway, and decided to make an landing on a taxiway. When the wings became level after the turn, he said both engines again restarted while in the vicinity of the beginning of the taxiway. As he was about to land, he said a car pulled out onto the taxiway, and stopped on the centerline, so he applied power to avoid the car. He said he climbed straight out, and when he made a climbing left turn, he said the engines ceased operating a third time, and the airplane descended towards a cluster of condos. With no runway or clear area in sight, the pilot said he guided the airplane to a retention pond. Follow-on/detailed examinations of the aircraft, engines, and propellers were conducted by an FAA Inspector, as well as technical representatives from Raytheon Aircraft Company, Pratt & Whitney Canada, and Hartzell Propeller Company, and no pre accident anomalies were noted with the airframe, flight controls, engines/accessories, or propellers. According to the FAA Inspector, and the technical representative from the airplane manufacturer, Raytheon Aircraft Company, the pilot was transferring fuel from the left fuel tank to the right fuel tank, and with the reduced amount of fuel in the left tank, as he performed left turns, the engine ceased operating. The Raytheon Aircraft Company representative stated that the Pilot Operating Handbook specifies the use of crossfeed for those times when the airplane is operating on a single engine.
Probable cause:
The pilot's inadequate management of the airplane's fuel system, which resulted in fuel starvation, a loss of engine power, a forced landing, and damage to the airplane during the landing.
Final Report:

Crash of a Piper PA-46-500TP Malibu Meridian in Port Orange: 2 killed

Date & Time: Dec 17, 2003 at 0933 LT
Operator:
Registration:
N155BM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Port Orange – Lufkin
MSN:
46-97053
YOM:
2001
Crew on board:
1
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1914
Captain / Total hours on type:
36.00
Aircraft flight hours:
30
Circumstances:
The airplane was destroyed when it impacted trees and terrain following an in-flight loss of control during climb after takeoff. Meteorological information indicates that the cloud ceilings were between 1,200 and 1,700 feet above ground level at the time of the accident. While airborne, the accident pilot reported to another pilot that the cloud ceiling was 1,500 feet. Radar data shows that the airplane flight profile became erratic once it had climbed above about 1,700 feet pressure altitude. The final flight path sequence depicted by the radar data shows a right-hand turn of decreasing radius with an associated rapid rate of descent. The last radar return coincided with the accident location. The non-instrument rated pilot had logged 7.0 hours of simulated instrument experience. The pilot had logged 35.8 hours in the same make and model as the accident airplane, of which, all but 0.3 hours was listed as crosscountry time. No records of training in the same make and model airplane were discovered. No pre-impact mechanical deficiencies were found during the post-accident examination of the wreckage.
Probable cause:
The unqualified pilot's continued flight into known instrument meteorological conditions which resulted in spatial disorientation and subsequent loss of aircraft control. Factors were the pilot's lack of instrument flight experience and the low ceiling.
Final Report:

Crash of a Piper PA-46-500TP Malibu Meridian in Vero Beach: 2 killed

Date & Time: Apr 9, 2001 at 1208 LT
Registration:
N262MM
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Vero Beach - Daytona Beach
MSN:
46-97040
YOM:
2001
Crew on board:
2
Crew fatalities:
Pax on board:
0
Pax fatalities:
Other fatalities:
Total fatalities:
2
Captain / Total flying hours:
1514
Captain / Total hours on type:
33.00
Copilot / Total flying hours:
378
Aircraft flight hours:
45
Circumstances:
Witnesses observed N262MM taxi to runway 29 left and the pilot perform what appeared to be a normal engine runup. The airplane then taxied onto runway 29 left for takeoff. The wind was from the east, making the takeoff with a tail wind. During the takeoff, the engine seemed to operate at a steady level, but appeared to be low on power. The flight lifted off about halfway down the runway and the landing gear was retracted. The airplane climbed slowly and turned slowly to the left. The airplane then entered a 60-80 degree left bank followed by the airplane rolling level and the wings rocking back and forth. The airplane was now on a southerly heading and the nose dropped. The airplane then collided with trees about 15-20 feet above the ground, fell to the ground, and burst into flames. Witnesses stated they saw no smoke or flames coming from the airplane prior to impact with the trees. At the time of the accident the landing gear was retracted and the engine was running. Transcripts of recorded communications show that at 1205:40, the local controller instructed the flight to taxi into position and hold on runway 29 left. At 1206:43, N262MM was cleared for takeoff and a north bound departure was approved. At 1208:03, the passenger transmitted "we need to land we have to turn around". The local controller cleared the flight to return to the airport when able. At 1208:20, the passenger transmitted "two mike mike we're going down we're going down", followed by "over the golf (unintelligible)". The local controller responded "copy over the golf course". No further transmissions were received from the flight. Analysis of background noise contained on the ATC recordings show that at the time the passenger on N262MM transmitted to controllers that they were ready for takeoff and when he acknowledged the takeoff clearance, the propeller was rotating at 1,261 and 1,255 respectively. When the passenger transmitted to controllers after takeoff, that they needed to land, the propeller was rotating at 1,980 rpm. When the passenger transmitted we have to turn around, shortly after the above transmission, the propeller was rotating at 2,017 rpm. When the passenger made his last transmission stating they were going down, the propeller rpm was 1,965. The maximum propeller speed at takeoff is 2,000 rpm. Additional evidence was found indicating electrical arcing and progressive fatigue cracking in the engine’s P3 line, which could result in a rapid rollback of engine power. Simulator testing showed that a P3 line failure would result in the engine decelerating from full takeoff power (2,000 propeller rpm) and stabilizing at an idle power setting in less than 9 seconds. However, the sound spectrum analysis of the first radio transmission indicated the propeller rpm was 1,980, and two subsequent radio transmissions, the last of which was made 17 seconds after the initial transmission, detected the propeller rpm at near takeoff speed. Thus, there was no evidence of dramatic rpm loss, making the P3 line failure an unlikely cause of the accident. Postcrash examination of the aircraft structure, flight controls, engine, and propeller, showed no evidence of failure or malfunction. Witnesses indicated the flight used about 3,650 feet of runway for takeoff or about half of the 7,296 foot long runway. Charts contained in the Piper PA-46-500TP, Pilot's Operating Handbook, indicated that for the conditions at the time of the accident, the airplane should have used about 2,000 feet of runway for the ground roll during the takeoff with no wing flaps extended. The charts also show that the airplane indicated stall speed at 60 degrees of bank angle with the landing gear and wing flaps retracted is 111 knots.
Probable cause:
The pilot's excessive bank angle and his failure to maintain airspeed while returning to the airport after takeoff due to an unspecified problem resulting in the airplane stalling and colliding with trees during the resultant uncontrolled descent.
Final Report:

Crash of a Convair CV-240-0 in Port Orange: 3 killed

Date & Time: May 24, 1980 at 1600 LT
Type of aircraft:
Operator:
Registration:
N300GR
Flight Phase:
Flight Type:
Survivors:
No
Schedule:
Port Orange - Santo Domingo
MSN:
115
YOM:
1948
Crew on board:
2
Crew fatalities:
Pax on board:
1
Pax fatalities:
Other fatalities:
Total fatalities:
6
Captain / Total flying hours:
7300
Captain / Total hours on type:
25.00
Circumstances:
During the takeoff roll at Port Orange-Spruce Creek Airport, the right engine caught fire and exploded. The crew failed to abort the takeoff and continued. During initial climb, the captain decided to attempt an emergency landing. The aircraft descended, crashed in a field and burst into flames. The aircraft was destroyed by fire and all three occupants were killed.
Probable cause:
Controlled collision with ground during initial climb after the crew attempted operation with known deficiencies in equipment. The following contributing factors were reported:
- The pilot-in-command failed to abort takeoff,
- Inadequate preflight preparation,
- Improperly loaded aircraft,
- Fire in engine,
- Forced landing off airport on land,
- The crew was aware that oil lines were 15 years old,
- The aircraft was approximately 7,353 lbs over gross weight for takeoff conditions.
Final Report: