Wednesday, May 21, 2025

Boeing 717-2BD, N942AT, incident occurred on February 24, 2025, at Atlanta Hartsfield-Jackson International Airport (ATL/KATL), Atlanta, Georgia

 This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

Aviation Investigation Report - National Transportation Safety Board

The National Transportation Safety Board did not travel the scene of this incident.

Investigator In Charge (IIC): Brazy, Douglass

Additional Participating Entities:

  • Patrick Lusch; FAA/AVP100; Washington, DC 
  • Josh Migdal; Delta Air Lines; Atlanta, GA 
  • Steve Haggarty; Boeing; Seattle , WA 
  • Richard Lewis; Rolls Royce; Bristol, OF 
  • Thomas Karge; BFU ; Braunschweig, OF 

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N942AT

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/199761/pdf


On February 24, 2025, at 0848 eastern standard time, Delta Air Lines flight 876, a Boeing 717- 200, N942AT, experienced smoke in the cabin and cockpit during takeoff from Atlanta Hartsfield/Jackson International Airport (ATL), Atlanta Georgia. The airplane returned to the airport, landed safely, and the crew conducted an emergency evacuation. There were 99 passengers and crew on board, and two passengers received minor injuries during the evacuation. The flight was conducted under the provisions of Title 14 Code of Federal Regulations Part 121 scheduled domestic passenger flight from ATL to Columbia Metro Airport (CAE), Columbia, South Carolina.


During the takeoff roll, flight attendants (FA) in both the forward and aft areas of the cabin saw smoke. The two FAs in the forward section first noticed it emanating from the area over the L1 door. The FA In the aft section first noticed it “coming out of all the vents”. Both the FA in the aft section and the lead FA in the forward section attempted to contact the pilots using the emergency call button but did not get a response. They also took turns using the interphone to try and announce to the pilots that there was smoke in the cabin. After takeoff, the lead FA also knocked on the cockpit door.


The aft flight attendant made a public address announcement to the passengers, advised that they were aware of and trained for the situation and to remain calm. The lead FA recalled that the smoke was very thick, and that he was unable to see past the first row of seats. A nonrevenue flight attendant who had been in a jumpseat, self-deployed to the exit row to prevent an unanticipated evacuation, or assist in evacuation if one ensued.


The pilots reported that just as the airplane rotated for takeoff, they heard the flight attendant call chime and knocking on the flight deck door. Shortly thereafter smoke was visible rising from the floor near the rear of the cockpit. They donned their oxygen masks and initially delayed responding to the flight attendant calls, as the captain focused on flying the airplane while first officer declared an emergency with air traffic control. 


Shortly after takeoff, a master caution alert for smoke detected in the forward lavatory occurred. The first officer began the quick reference handbook (QRH) checklist for this alert and then attempted to communicate with the cabin crew using the handset phone. He recalled that he could hear the cabin crew, but when he spoke, they could not hear him. As the lead FA began to unlock the cockpit door, he was able to hear the first officer on the interphone advise that the pilots were aware and returning to the airport. The lead FA then relayed that information to the other cabin crew and passengers. 


Soon after, an alarm warning of low oil pressure for the right engine occurred in the cockpit. The crew performed the QRH procedure which ultimately led them to shut down the right engine.


As the airplane was returning to the airport, the captain elected to change the approach from runway 27R to 27L “in order to get glidepath guidance since our visibility was restricted due to the smoke and the facemask”. The remainder of the approach and landing were uneventful.


The crew stopped the airplane on the runway after landing and the airport rescue and fire fighting vehicles arrived soon after. The pilots opened the flight deck door, noticed a “tremendous” amount of smoke in the cabin, and the captain immediately ordered an evacuation. The aft FA coordinated the evacuation through the tailcone door with no anomalies. The lead FA managed door 1L, which he initially had some difficulty opening but succeeded on his 3rd attempt. The 3rd FA managed the evacuation through the 1R door with no anomalies.


The non-revenue FA managed the overwing emergency exits evacuation. She remained on the wing with some passengers who were unable to jump from the wing to the ground. The airplane does not have evacuation slides for the overwing exits, the egress path is to slide down the trailing edge of the wing. The wing flaps were extended to 25° prior to the evacuation (in accordance with the checklist) to reduce the height from the wing to ground.


She coordinated with the other three FAs and they determined at that time, because there were no remaining risks inside or outside the cabin, the passengers remaining on both wings could reenter the cabin and evacuate using the 3 usable deployed doors slides.


The airplane was equipped with Rolls Royce model BR715-C1 engines. During a post incident examination, maintenance personnel found no oil visible in the sight glass of the right engine oil reservoir, indicating the quantity was at or near zero. Examination of the right engine’s components continues.


Qualified parties were invited to participate in the investigation. These included the Federal Aviation Administration (FAA), Delta Air Lines, and Boeing Commercial Airplanes. In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Federal Bureau of Aircraft Accidents Investigation (BFU) of Germany, the State of Manufacture for the engines, was appointed to support the investigation with Rolls Royce as a technical advisor.


An NTSB flight data recorder specialist has been assigned. The investigation continues. 

Cessna 421C Golden Eagle, N245T, fatal accident occurred on June 17, 2024, near Steamboat Springs Airport/Bob Adams Field (SBS/KSBS), Steamboat Springs, Colorado

The National Transportation Safety Board travelled to the scene of this accident.

Investigator In Charge (IIC): Aguilera, Jason

Additional Participating Entities:

  • Harold Robertson; FAA FSDO; Denver, CO 
  • PJ Beavers; Textron Aviation; Wichita, KS 
  • Ernie Hall; Textron Aviation; Wichita, KS 
  • J Ferrell; Continental Motors; Mobile, AL 

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/194487/pdf

https://data.ntsb.gov/Docket?ProjectID=194487

http://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N245T

  • Location: Steamboat Springs, Colorado 
  • Accident Number: CEN24FA228 
  • Date & Time: June 17, 2024, 16:23 Local 
  • Registration: N245T 
  • Aircraft: Cessna 421 
  • Aircraft Damage: Destroyed 
  • Defining Event: Loss of control in flight 
  • Injuries: 2 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal 

On June 17, 2024, about 1623 mountain daylight time, a Cessna 421C airplane, N245T, was destroyed when it was involved in an accident near Steamboat Springs, Colorado. The pilot and passenger were fatally injured. The airplane was operated under the provisions of Title 14 Code of Federal Regulations Part 91 as a personal flight.


While enroute to the destination airport, the pilot reported a “cylinder temperature issue' to air traffic control (ATC) and the pilot diverted to another airport for a visual approach. The pilot overflew the airport and requested vectors for another visual approach. He then requested vectors to divert to an airport to the east before he informed air traffic control that the left engine lost power, and he received vectors back to the airport for a visual approach. The pilot maneuvered the airplane to land on runway 14, but for an unknown reason he decided to land on runway 32 instead. A pilot-rated witness reported that he observed the airplane while it was on the base to final turn for runway 32.  He reported that the airplane's wings leveled momentarily before it made a 60° left-bank turn and then entered a stall/spin in a counterclockwise rotation. The airplane impacted a trailer park about 0.38 miles from the approach end of runway 32. A postimpact fire ensued and destroyed the airplane.


Examination of the airframe, flight controls, and the right engine did not detect any preimpact anomalies that would have precluded normal operation.


Examination of the left engine found that the starter adapter spline was worn, with broken teeth on its crankshaft gear. The crankshaft gear remained properly timed with the crankshaft cluster gear, the investigation could not determine if the idler gear, which drives the magnetos, slipped timing. Mistiming of the magnetos could result in abnormal cylinder head temperature(s). In addition, there was improper hardware securing the cylinder No. 6 intake valve, which might have altered performance of that valve. Due to thermal damage, testing of the ignition and fuel systems could not be accomplished. Evidence of detonation was observed on the left engine's piston heads. The installed engine data monitor was destroyed by the postimpact fire and did not provide further details as to the operational condition of the engine before the accident. 


Inspection of the starter adapter assembly is required annually by airworthiness directive and was accomplished on the most recent annual inspection. The airplane had flown at least 4.5 hours since the inspection.


- Probable Cause: 

The pilot's failure to maintain sufficient airspeed following a loss of engine power, which resulted in an inadvertent aerodynamic stall/spin at low altitude.

American Champion 8GCBC Scout, N23BD, fatal accident occurred on September 1, 2024, near Meeteetse, Wyoming

The National Transportation Safety Board travelled to the scene of this accident.

Investigator In Charge (IIC): Gutierrez, Eric

Additional Participating Entities:

  • Bruce Hanson; Federal Aviation Administration; Denver, CO 
  • David Harsanyi; Lycoming Engines; Williamsport, PA 

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/195035/pdf

https://data.ntsb.gov/Docket?ProjectID=195035

http://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N23BD

  • Location: Meeteetse, Wyoming 
  • Accident Number: WPR24FA291 
  • Date & Time: September 1, 2024, 10:45 Local 
  • Registration: N23BD 
  • Aircraft: AMERICAN CHAMPION AIRCRAFT 8GCBC 
  • Aircraft Damage: Destroyed 
  • Defining Event: Loss of engine power (partial) 
  • Injuries: 1 Fatal, 1 Serious
  •  Flight Conducted Under: Part 91: General aviation - Personal 


On September 1, 2024, about 1045 mountain daylight time, an American Champion Aircraft 8GCBC, N23BD, was destroyed when it was involved in an accident near Meeteetse, Wyoming. The pilot sustained serious injuries, and the passenger was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.


The pilot reported that the purpose of the flight was to fly to a predetermined location in a nearby national forest, locate the passenger's relatives on the ground, and spread the ashes of the passenger's recently deceased family member. After arriving at the location, they observed the family members on the ground, circled, and spread the ashes. After releasing the ashes, the pilot leveled the airplane and applied engine power. He stated that the airplane “reached an altitude where it could not climb' and that the airspeed was near stall speed. He did not recall the airplane's altitude at the time it stopped climbing, and reported that due to his injuries, he did not recall any of the subsequent events of the flight.      


ADS-B flight track data showed that the airplane departed the airport and flew in a southerly direction toward the national forest. The data depicted a series of heading and altitude changes that were consistent with the family member's statement. The airplane then departed to the southwest along a valley toward an area of rising terrain. The airplane began to climb from about 8,550 ft mean sea level (msl) with a corresponding decrease in groundspeed until flight track data ended in the vicinity of the accident site. The airplane's last recorded altitude and groundspeed was 9,625 ft msl and 63 knots, respectively.


A pilot-rated witness did not observe the accident sequence, but did hear a sputtering engine followed by the sound of the accident airplane impacting terrain with a “loud bang.' He then observed black smoke emanating from a group of trees about 3/4 mile from his location.

The airplane impacted mountainous terrain along the southern edge of a valley at an elevation of 9,850 ft mean sea level. All major structural components of the airplane were located near the main wreckage. The airplane was mostly consumed by post impact fire. The engine remained attached to the engine mount and fuselage. Thermal damage was observed throughout the engine from post impact fire. Disassembly of the engine revealed a slight bend on the crank shaft about mid span, consistent with impact damage. 


Even though the witness report of a sputtering engine could not be corroborated due to the extensive thermal damage from the post-crash fire, ADS-B data indicated that the airplane continued to climb until the collision with rising terrain. Although the airplane's climb performance could not be assessed, the airplane's controlled flight into terrain was consistent with the pilot's decision to continue the flight with the airplane approaching its maximum gross weight at a low altitude in a high-elevation, high-density-altitude environment.


- Probable Cause: 

The pilot's decision to continue the flight over rising terrain at a low altitude in a high-elevation, high-density-altitude environment.

Tuesday, May 20, 2025

Cessna 172RG Cutlass RG, N6386V, accident occurred on April 23, 2025, at Triangle North Executive Airport (LHZ/KLHZ), Louisburg, North Carolina

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

Aviation Accident Preliminary Report - National Transportation Safety Board

The National Transportation Safety Board did not travel the scene of this incident.

Investigator In Charge (IIC): Young, Joshua

Additional Participating Entities:

  • Susan Adolwa; FAA/FSDO; Greensboro, NC

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N6386V

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200073/pdf

  • Location: Louisburg, NC
  • Incident Number: ERA25LA188
  • Date & Time: April 23, 2025, 17:03 Local
  • Registration: N6386V
  • Aircraft: Cessna 172RG  
  • Injuries: 2 None 
  • Flight Conducted Under: Part 91: General aviation - Personal


On April 23, 2025, about 1703 eastern daylight time, a Cessna 172RG, N6386V, was substantially damaged when it was involved in an accident near Louisburg, North Carolina. The commercial pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot reported that he performed a preflight inspection of the airplane. During the inspection, he found water while sampling fuel from the fuel tanks. The pilot continued to sample fuel from the fuel tanks until no more water was found. He then rocked the wings to release any trapped water and sampled fuel from the fuel tanks again until there was no water found. He reported that the wing fuel tanks were about half full of fuel.

The engine start and run-up were normal, with no abnormalities noted by the pilot. About 1702, the pilot entered the runway and applied full power for takeoff. With all engine indications normal, he released the brakes and began the takeoff roll. When the airplane reached an airspeed of 55 knots, the pilot increased the airplane’s pitch attitude and began climbing out at an airspeed 70 knots. When no usable runway remained, the pilot selected the landing gear to the up position, and he reported “the moment the landing pump switched on the engine lost power.” The pilot described the loss of power as a smooth reduction of power to idle, where the engine stayed. He selected the landing gear to the down position, reduced the throttle control, and attempted to land on the remaining runway and runoff area. After realizing he could not, he attempted to glide over an airport perimeter fence. During the glide, he applied full throttle, and the engine revved to about 1,900 rpm before reducing uncommanded again to idle. The landing gear impacted the perimeter fence, the horizontal stabilizer impacted a fence pole, and the airplane impacted a road near the airport perimeter, sliding off the road and into a field. The horizontal stabilizer sustained substantial damage during the accident sequence.

The wreckage was retained for further examination.

Airbus A321-271NX, N607FR, incident occurred on April 15, 2025, at San Juan-Luis Muñoz Marín International Airport (SJU/TJSJ), San Juan, Puerto Rico

This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

Aviation Accident Preliminary Report - National Transportation Safety Board

The National Transportation Safety Board did not travel the scene of this incident.

Investigator In Charge (IIC): Hauf, Michael

Additional Participating Entities:

  • Andy Olvis; FAA 
  • Shawn Christiansen; Frontier Airlines 
  • Doug Zabawa; Pratt &Whitney 
  • Thierry Rozec; BEA Helene Carrols; Airbus 
  • Simon Sheldon; EASA 
  • Ryan Greene; ALPA 

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N607FR

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200025/pdf

  • Location: San Juan, PR 
  • Incident Number: DCA25LA184 
  • Date & Time: April 15, 2025, 21:40 Local 
  • Registration: N607FR 
  • Aircraft: Airbus A321-271NX 
  • Injuries: 235 None 
  • Flight Conducted Under: Part 121: Air carrier - Scheduled

On April 15, 2025, about 2140, Atlantic daylight time (ADT), Frontier Airlines, flight 3506, an Airbus A321-271NX, N607FR, sustained nose wheel and engine damage during an attempted landing at the Luis Munoz Marin International Airport (SJU), San Juan, Puerto Rico. The 235 passengers and crew onboard were uninjured. The flight was operated as a Title 14 Code of Federal Regulations Part 121 scheduled domestic passenger flight from Orlando International Airport (MCO), Orlando, Florida to SJU.


According to the flight crew, the first officer (FO) was the pilot flying, and the captain was the pilot monitoring during the night flight to SJU. The approach was stable but required a slight lateral correction to maintain centerline while descending through about 150 to 100 feet above ground level (agl) on approach to runway 10.


An aural RETARD alert is designed to occur at a radio altitude (RA) of 20 ft on manual landing to advise the flight crew to reduce the thrust levers to idle. The FO recalled that during the approach, she brought the thrust levers back to idle at 20 ft RA while the RETARD aural alert sounded.


The captain recalled that the landing flare began normally but became high at about 15 ft RA. The FO stated that around 15 ft RA, the captain noted that the aircraft was too high, so she corrected with a shallow descent and then a gradual flare. As the aircraft was about to touch down, the captain called for a go-around. The captain stated that he believed the aircraft was “running out of flying speed quickly, as the throttles were retarded and the pitch attitude was increasing” so he assumed control. He recalled that the airplane was slightly nose down with the thrust at the takeoff/go-around (TOGA) setting when the airplane then touched down firmly.


The captain stated that during the go-around, they heard a loud bang coming from under the fuselage and the FO called out that an engine failure was displayed on the electronic centralized aircraft monitor (ECAM) display.


The air traffic control tower (ATCT) controller reported an engine fire, but according to the flight crew, they only had an indication of an engine failure. Unsure of the damage sustained, the captain asked for a foreign object debris (FOD) sweep of the runway and a description of any debris found. Some metal and tire debris were found on the runway and reported to the flight crew.


The captain stated that he flew a low pass by the ATCT to see if the controllers could determine if all three landing gear appeared to be down. The ATCT controller reported that the landing gear was intact, and the flight crew prepared for a visual approach to runway 8. At touchdown, the airplane behaved normally so the captain elected to clear the runway and set the parking brake as the fire department approached to inspect the number one engine for any fire. No fire was present, and the captain elected to coordinate for airstairs to deplane the aircraft rather than using the evacuation slides. He felt there was no threat to life and the slides posed a greater danger to passengers than the airstairs. He also noted that there were 8 wheelchair passengers on board. The passengers were unloaded via airstairs and bussed to the terminal.


Investigation

On March 16, 2025, the National Transportation Safety Board (NTSB) was notified by Frontier Airlines about the event and, in response, began an incident investigation. As part of the investigative process, the NTSB invited qualified parties to participate in the investigation. These included the Federal Aviation Administration (FAA), Frontier Airlines, the Air Line Pilots Association, International (ALPA), and Pratt & Whitney. In accordance with the provisions of Annex 13 to the Convention on International Civil Aviation, an Accredited Representative from the Bureau d'Enquêtes et d'Analyses (BEA) of France, the State of Design and Manufacture of the airplane, was appointed to support the investigation, with Airbus and EASA as technical advisors.


NTSB group chairs in the areas of operations, human performance, and flight data recorders were assigned. The flight data recorder (FDR) and the cockpit voice recorder (CVR) were removed from the airplane and shipped to the NTSB’s Vehicle Recorder Laboratory located in Washington, DC, for analysis. A preliminary review of the FDR has been completed and a plot showing several parameters is shown in figure 1. The data revealed that the airplane initially touched down on all three landing gear with a maximum recorded vertical acceleration of about 2.2g. This value is above the hard landing threshold of 1.8g per Frontier Airlines aircraft maintenance manual (AMM) Chapter 5 limitations.



A post incident inspection of the airplane revealed that the nose landing gear (NLG) left wheel and tire had separated from its axle and departed the aircraft after the initial hard landing (figure 2). One of the wheel halves had fractured and there were numerous scratches and gouges noted on the NLG along with damage to the tow fitting. Metal fragments from the wheel assembly appear to have been ingested by the number one (left) engine and damage was found on the engine's inlet cowl liner, thrust reverser, fan blades, and guide vanes. The left inboard trailing edge flaps were also damaged. None of this damage met the definition of substantial damage or affected the flight control system of the airplane.


On May 5-6, 2025, the operational factors group, with assistance from an NTSB Human Performance Specialist convened in Denver, Colorado. The group interviewed the Frontier airlines flight crew, the Director of Training and the Director of Operations.


In January 2021, an article titled “A Focus on the Landing Flare” was published by Airbus in their Safety First magazine. The article analyzes two case studies to highlight operational pitfalls and reinforce best practices during the flare phase of landing. You can read the full article on Airbus’s official Safety First website here: A Focus on the Landing Flare.


The investigation continues.

Saturday, May 17, 2025

Cessna 182 Skylane, N9415M, accident occurred on May 3, 2025, near Kentwood, Louisiana

 This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

Aviation Accident Preliminary Report - National Transportation Safety Board

The National Transportation Safety Board did not travel the scene of this accident.

Investigator In Charge (IIC): Lindberg, Joshua

Additional Participating Entities:

Mark Lazard; FAA; Baton Rouge, LA 

Julie Crowell; Continental Motors; Mobile, AL 

Casey Love; Textron Aviation; Wichita, KS 

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N98416

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200099/pdf

  • Location: Kentwood, LA 
  • Accident Number: CEN25LA169 
  • Date & Time: May 3, 2025, 15:30 Local 
  • Registration: N9415M 
  • Aircraft: Cessna 182P 
  • Injuries: 1 Serious, 1 Minor
  • Flight Conducted Under: Part 91: General aviation - Personal

On May 3, 2025, about 1530 central daylight time, a Cessna 182P, N9415M, was substantially damaged when it was involved in an accident near Kentwood, Louisiana. The pilot sustained serious injuries, and the passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot stated that he intended to depart from a 2,600 ft private grass strip, which was surrounded by trees on both sides. Before takeoff he completed an engine runup with no issues noted and ensured the flight controls were free and correct. He extended the flaps to 20° and verified the pitch trim was in the takeoff position. During the initial climb and after the airplane was clear of the treetops, he turned left toward the destination airport when the airplane made an uncommanded and abrupt pitch up. He attempted to decrease the pitch attitude with the control yoke and adjust the pitch trim, but the airplane continued to pitch up. The stall warning horn sounded, and the airplane descended into tress and terrain. The passenger was able to release her seat belt and remove herself and the pilot from the airplane. The airplane sustained substantial damage and there was no postimpact fire.

The last airframe annual inspection and engine 100-hour inspection were completed on July 14, 2024. There were no unresolved discrepancies noted in the logbook entries for these inspections.

The airplane has been retained for further examination. 

Piper PA-32RT-300 Lance II, N30689, fatal accident occurred on May 10, 2025, near Nassau Airport (83FL), Yulee, FL

 This is preliminary information, subject to change, and may contain errors. Any errors in this report will be corrected when the final report has been completed.

Aviation Accident Preliminary Report - National Transportation Safety Board

The National Transportation Safety Board travelled to the scene of this accident.

Investigator In Charge (IIC): Young, Joshua

Additional Participating Entities:

Bradford Holland; FAA/FSDO; Orlando, FL 

Kris Wetherell; Piper Aircraft; Vero Beach, FL 

Dave Harsanyi; Lycoming Engines; Williamsport, PA

https://registry.faa.gov/AircraftInquiry/Search/NNumberResult?nNumberTxt=N30689

https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/200140/pdf

  • Location: Yulee, FL 
  • Accident Number: ERA25FA201 
  • Date & Time: May 10, 2025, 09:35 Local 
  • Registration: N30689 
  • Aircraft: Piper PA32RT Injuries: 1 Fatal 
  • Flight Conducted Under: Part 91: General aviation - Personal

On May 10, 2025, about 0935 eastern daylight time, a Piper PA-32RT-300, N30689, was destroyed when it was involved in an accident near Yulee, Florida. The private pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot’s wife reported that the purpose of the flight was for the pilot to reposition the airplane from Nassau Airport (83FL), Yulee, Florida to Fernandina Beach Municipal Airport (FHB), Fernandina Beach, Florida, where they would wait for approaching thunderstorms to pass through the area before continuing on to Tennessee. She reported that earlier that morning, the pilot had dropped her and their dogs off at FHB before driving back to 83FL where he planned to finish loading the airplane for their trip and make the short flight to FHB.

Review of video captured by a motion-activated surveillance camera mounted on a hangar near the end of runway 12 at 83FL showed that the airplane taxied toward runway 12 and began a back taxi down the runway and out of the video frame (figure 1). During the taxi the airplane’s nose baggage door was closed. As the video continued, the airplane re entered the frame on a takeoff roll at 0934. The video showed that during the takeoff, the nose baggage door was open. The door stayed open until the airplane became airborne and exited the video frame. Following the accident, a sweep of the usable portion of runway 12 found a case of aviation oil about 100 ft from the beginning of the runway and to the right of centerline. A bag of dog food was also found about 440 ft from the beginning of the runway and to the right of centerline. Review of surveillance video from a residence that was located about 550 ft north of the departure end of the runway showed the airplane in a steep left wing low descent prior to impacting a tree and the ground about 10 seconds after departing 83FL.



The wreckage was examined at the accident. The initial impact point was identified as a broken branch about 40 ft up a tree. A crater in the ground was identified about 24 feet away from the tree, and the wreckage came to rest upright about 15 ft from the crater, on a heading of 264° magnetic. The calculated angle of descent between the initial tree impact and the crater was about 50°. An 84-inch-long outboard portion of the left wing was impact-separated and remained near the crater with the left aileron attached.

The cockpit and a majority of the fuselage were consumed by postimpact fire. The left flap, right wing, rudder, vertical stabilizer, and a majority of the stabilator and stabilator trim were also consumed by the postimpact fire. Aileron flight control continuity was confirmed from the aileron bellcranks to the flight control attachment points in the cockpit. Rudder flight control continuity was confirmed from the rudder control drum to the rudder pedals in the cockpit. Stabilator control continuity was confirmed from the stabilator control bellcrank to the lower portion of the cockpit control. The stabilator trim actuator was measured and equated to a trim setting halfway between full nose down and neutral.

The three-blade propeller remained attached to the engine crankshaft flange. The propeller blades exhibited aft bending and chordwise scratching. Engine crankshaft and valvetrain continuity was established when the propeller was rotated 720°. Thumb suction and compression were observed on all cylinders. The vacuum pump remained attached to the engine accessory case; the drive gear and carbon veins all remained intact. The left standard magneto and right electronic magneto were removed and exhibited thermal damage. The fuel pump exhibited impact and thermal damage. The fuel injector assembly was impact separated and exhibited thermal damage. The sparkplugs were removed and exhibited normal wear and coloration consistent with normal engine operation when compared to the Champion Aviation Check-A-Plug AV-27 chart. The fuel injector nozzles were removed and were free of debris. The postimpact fire consumed most of the airplane’s fuel system. Both main wing fuel tanks were breached and exhibited thermal damage. 

The wreckage was retained for further examination.

The pilot’s wife reported that several weeks before the accident, she and the pilot had flown from Clearwater Air Park (CLW), Clearwater, FL to 83FL, a flight that was about 1 hour long. She reported that they had fully fueled the airplane prior to that flight and that the accident flight was the first flight since. She also described that 83FL did not have fuel services and they did not add any fuel to the airplane after the flight from CLW to 83FL. Preliminary review of the Piper PA-32RT-300 Pilot Operating Handbook showed the airplane had an endurance between 5 and 7 hours depending on the power setting used.

Preliminary review of weather radar data showed a line of intense precipitation echoes moving through the area at the time of the accident. A weather station at FHB, which was located about 3 nautical miles east of the accident site, reported at 0935 that the wind was from 180° true at 5 knots, 10 statute miles of visibility, and scattered clouds at 2,300 ft above ground level with thunderstorms in the vicinity and lightning distant southwest through north. The same station reported at 0955 wind from 320° at 13 knots gusting to 20 knots, 2 statute miles of visibility in heavy rain and thunderstorms, overcast clouds at 2,100 ft above ground level, and lightning in all quadrants.