A bit late today, had an early morning flying opportunity I could not say no to, and then ran into some website issues.
Looks like we're back on track so let's give this a go, here are your stories to kick off the week...
Be safe out there!
Tom
-
No injuries after plane makes belly landing at Page Field
Layza Pinero Resto - Assignment Editor
FORT MYERS, Fla. —
A private aircraft made a belly landing at Page Field in Fort Myers on Saturday morning, forcing other pilots to divert and attracting onlookers to the observation area. 
Elvis Gonzalez, a pilot, said he was in the air when he was told to change his landing location.
“Well, we were coming back from the south. And as we get ready to land, they told us there was an emergency and we couldn’t land. So we had to keep flying to the north,” Gonzalez said.
Gonzalez, who was at the scene with fellow pilot Daniel Gonzalez, said it was the first time he had seen a belly landing involving a large aircraft.
“The first time that I’ve seen something. I mean, I saw one before but it was a small airplane. But something like this big? No, this is the first time,” Gonzalez said.
The port authority said the private Cessna experienced a landing gear issue, which led to the belly landing. This type of landing occurs when an aircraft lands without its landing gear extended.
Raymond Kuczera, a Navy veteran who spends his mornings at the observation area, said he saw the landing unfold.
“I’ve seen when the plane evidently hit the ground, it was just flying. And then it would taxi out to go to the terminal. Evidently the landing gear must have collapsed,” Kuczera said.
The port authority confirmed there were two people on board the aircraft. No injuries were reported, and the airport remains open.
https://www.gulfcoastnewsnow.com/article/plane-belly-landing-page-field-fort-myers-florida/71259131
Frontier Airlines jet bound for LAX hits, kills person on runway during takeoff in Denver
The person was at least partially consumed by one of the engines, igniting a massive engine fire that filled the plane with smoke. 
A Frontier Airlines flight headed to Los Angeles struck and killed a person who reportedly scaled a fence and ran onto a runway during takeoff Friday night at Denver International Airport.
The incident happened at around 11:19 p.m. MT Friday when Frontier Flight 4345 reported striking a pedestrian during takeoff, according to a statement from Denver International Airport.
“Statement from DEN on incident tonight: Frontier Flight 4345 reported striking a pedestrian during takeoff at DEN at approximately 11:19 p.m. on Friday, May 8, 2026. There was a brief engine fire that was promptly extinguished by the Denver Fire Dept. (1/2)”
The person was at least partially consumed by one of the engines, an official confirmed to ABC News, igniting a massive engine fire. Passengers said smoke filled the plane within seconds.
Some people who were on the flight finally reached LAX on Saturday morning. Eyewitness News spoke to some of the passengers.
"It was like boom! And then you see the flames come, and then the smoke comes, and it's just horrible," said passenger Vanilla Ellis.
"And I'm just waiting for the masks to come down, and they never come down. So everyone's having struggle, like, we're struggling breathing. We are like, panicking," passenger Brandon Dee said. "Someone said that they're going to punch the window open. People are recording. I'm just covering my mouth. I'm just trying to like, stay calm."
There were 224 passengers and 7 crew members on board, Frontier said.
Passengers evacuated the aircraft on the runway via slides and were bused to terminals by emergency crews.
All those onboard the plane were evaluated, which is standard procedure following an evacuation.
Preliminary reports are that 12 were injured and five were taken to the hospital, according to the Transportation Secretary Sean Duffy.
"They had us go into lines when everyone got off the plane. And they went up and down and said, like, 'Is anybody injured? Does anybody need to go to the hospital? Is anybody injured?'" said passenger Chloe Kuns. "And yeah, they checked in on us. They were doing the best they could."
Air traffic control audio from ATC.com captured the crew reporting the emergency to the tower.
"Tower, Frontier 4345, we're stopping on the runway. Uh, we just hit somebody... we have an engine fire," the pilot is heard on the audio from ATC.
When asked how many people were aboard, the pilot responded, "We have 231 souls on board... There was an individual walking across the runway."
Moments later, the pilot reported the need to evacuate.
"We've got smoke on the aircraft, we're gonna evacuate on the runway," the pilot said.
The Denver Fire Department responded to the scene and extinguished the fire.
Duffy said Saturday the victim had breached airport security, deliberately scaled a perimeter fence, and ran onto the runway. The person was struck by the plane during takeoff at high speed, Duffy said.
Frontier Airlines released the following statement:
"As flight 4345 was departing this evening from Denver International Airport to Los Angeles International Airport, the aircraft reportedly struck a pedestrian on the runway during takeoff. Smoke was reported in the cabin, and the pilots aborted takeoff. Passengers were then safely evacuated via slides as a matter of precaution. The Airbus A321 was carrying 224 passengers and seven crew members. We are investigating this incident and gathering more information in coordination with the airport and other safety authorities. We are deeply saddened by this event."
A source briefed on the incident told ABC News that airport security was inspecting the east perimeter fence on Saturday morning for gaps, and the person struck did not appear to be connected to the work occurring on a parallel runway.
The Denver airport later confirmed the person impacted by the jet is not believed to be an employee of the airport, nor have they been identified.
Local law enforcement handles airport security and is investigating the breach with support from the Federal Aviation Administration and Transportation Security Administration, Duffy said.
"Emergency response and investigation are ongoing," the Denver International Airport said earlier. "The NTSB has been notified. Runway 17L will remain closed while the investigation is conducted."
ABC News contributed to this report.
https://abc7.com/post/frontier-airlines-jet-bound-lax-strikes-person-denver-runway-engine-fire-forces-evacuation/19068264/
A plane collides with a bird mid-flight, triggering alarms during its landing in Palma.
Emergency teams have evacuated the passengers, among whom are numerous representatives of the Mallorcan tourism sector. 
Nerves, shouts, and anxiety gripped the passengers of Air Europa flight UX6079, which landed in Palma on Friday afternoon with a problem in the aircraft's steering control . The incident, which occurred around 8:30 p.m., caused quite a stir at Son Sant Joan Airport , although fortunately, no one was injured thanks to the quick and efficient response of the flight crew and the technical and emergency services stationed on the tarmac at Palma Airport .
According to the company's explanation after analyzing the incident, the plane , which had departed from Madrid, struck a bird during flight ; although no problems were reported immediately after the collision. Shortly afterward, while landing on the airport's North runway, the pilots detected a malfunction in the aircraft's steering control system, caused, according to the leading hypothesis, by the earlier bird strike.
The aircraft managed to land without leaving the runway, although it skidded and came to rest in an unusual position . Emergency services were immediately activated at Son Sant Joan Airport, with several fire trucks and technical personnel on the scene.
Air traffic control blocked activity in the area while emergency operations were underway, and passengers remained inside the aircraft until their safety during disembarkation could be guaranteed. A large group of people linked to the Mallorcan hotel and tourism sector were also on board . Among the passengers were Encarna Piñero, Javier Vich, Pere Joan Planas, and Juan Carlos Tárraga, an executive at WTW.
At approximately 9:30 p.m., after the most anxious moments had passed, the company issued a statement describing the incident: “An Air Europa Express aircraft operating the Madrid-Palma route was struck by a bird. During the landing maneuver, a problem was detected in the aircraft's steering control system . The aircraft remained within the runway boundaries at all times and did not leave the runway. No injuries were reported among passengers or crew. After the aircraft was immobilized, it was removed from the runway and the passengers disembarked without incident.”
According to Aena, the aircraft veered off the runway and came to a stop in an exit taxiway. As a result, five flights were diverted: three were redirected to Ibiza and two to Menorca, later resuming their normal schedules.
An hour after the alarming incident, the airport has resumed normal operations; although while the blockade was in place, routes landing in that area were notified and some flights were diverted to alternative airports , as reported from the 'Air Traffic Controllers' account of X.
The passengers experienced a harrowing situation, although fortunately, and as confirmed by passengers themselves from inside the aircraft, no one was injured . However, there were delays and waits due to security measures, and the spacing between arriving flights was increased to allow for the scheduling of pending departures.
https://www.ultimahora.es/noticias/local/2026/05/08/2625889/avion-pierde-rueda-durante-aterrizaje-aeropuerto-palma.html
Small plane flips upside down during emergency landing in Polk County
Sierra Rains
POLK COUNTY, Fla. (WFLA) — A pilot walked away
without a scratch after his plane flipped upside down during an emergency landing west of Mulberry on Friday night, the Polk County Sheriff’s Office said.
The sheriff’s office said deputies received reports of a plane crash just after 8 p.m. When deputies arrived at the scene, not far from the South Lakeland Airport, they found the pilot uninjured.
Officials said the pilot was the only person on board the aircraft, which was described as a one-seat, fixed-wing plane.
He had just taken off from the South Lakeland Airport when the plane experienced engine trouble. The pilot then found a grassy area near SR 60 and County Line Road where he could land the plane.
According to officials, the plane flipped over as it was slowing to a stop on the ground.
“Pilot is fine, not even a scratch,” a spokesperson for the sheriff’s office said.
Deputies remained on scene Friday night and said they were notifying the necessary agencies.
https://www.wfla.com/news/polk-county/small-plane-flips-upside-down-during-emergency-landing-in-polk-county/amp/
Two unharmed after emergency plane landing in rural Grant County
By Dan Thesman
MOSES LAKE — Two people escaped injury Friday
morning after a light aircraft was forced into an emergency landing in a rural area of Grant County, authorities said.
First responders were dispatched to the 16000 block of Road P.5-Northeast following reports of an aircraft emergency in the Black Rock area, located approximately 16 miles northeast of Moses Lake.
The Grant County Sheriff’s Office confirmed that incident commanders at the scene located the aircraft and its two occupants shortly after the initial call. By 9:30 a.m., officials verified that neither individual on board sustained injuries during the incident.
Authorities have not yet released the cause of the emergency or the flight’s intended destination. The identity of the pilot and passenger were also withheld.
The Federal Aviation Administration typically investigates reports involving aircraft emergencies. No further details were immediately available.
https://elkhornmediagroup.com/two-unharmed-after-emergency-plane-landing-in-rural-grant-county/
Gol cargo plane veers off runway after landing in Salvador.
The incident happened on Saturday morning (9) and no one was injured. The track was wet due to rain and there was fog in the area.
By g1 BA
A GOL cargo plane went off the runway after landing at
Salvador airport on Saturday morning (9). According to the airline, there were no passengers on board and the crew were not injured in the incident.
There is still no information about what caused the incident, but at the time of landing the runway was wet due to light rain and there was fog in the area.
Incidents like the one in Salvador are known as "runway excursions," when a plane fails to stop in time.
According to the company, flight G39618, which departed from Guarulhos (SP) bound for Salvador (BA), is in the airport's security area. It is a 2007 Boeing 737.
Vinci Airports, the concessionaire that operates Salvador International Airport, reported that, following the incident, the auxiliary runway was closed so that the competent authorities could remove the aircraft and complete the investigations.
The airport continues to operate normally via the main runway, which was not affected.
https://g1.globo.com/ba/bahia/noticia/2026/05/09/aviao-cargueiro-da-gol-salvador.ghtml
Plane lands on Manitoba highway
By Devon McKendrick
A Manitoba highway was closed for a short time Friday afternoon after a plane landed on it. 
Manitoba RCMP said officers from the Powerview detachment were called around 12:30 p.m. for reports that a plane had landed on Highway 304.
A spokesperson for the Transportation Safety Board (TSB) said the Piper aircraft was flying from the St. Andrews Airport to Red Sucker Lake on Friday when the plane “experienced an engine issue.”
There were six people and the pilot on board. TSB said the plane landed safely and no one was injured. The plane was also not damaged during the landing.
Pictures from the scene show the small plane sitting in the middle of the road with a backlog of traffic on either side.
The road was closed for a couple of hours, but it has since been reopened.
TSB said it is still gathering information about the incident.
https://www.ctvnews.ca/winnipeg/article/plane-lands-on-manitoba-highway/
Plane crashes on Monroe Mountain
BY PARLY SCOTT - KSLNewsRadio
MARYSVALE, Piute County — A plane crashed on Monroe Mountain on Sunday afternoon, according to Marysvale Fire Department. 
According to police, the plane held a 59-year-old man and an 88-year-old man.
The 88-year-old was airlifted to Utah Valley Hospital for medical treatment.
The 59-year-old was transported by private vehicle.
As a result of the crash, the aircraft started a small wildfire.
DNR Fire and the U.S. Forest Service responded, and the fire was quickly contained to one acre.
The Piute Sheriff’s Office, MVFD, and Monroe Fire Department also responded.
The police are still investigating the cause of the crash.
NTSB Prelim: Cessna 401B
Witness Observed The Airplane Enter A Descending Left Turn, Followed By A Brief Right Turn And A Slight Climb, Before It “Dropped Out Of The Sky.”
Location: Land O' Lakes, FL Accident Number: ERA26FA179
Date & Time: April 19, 2026, 08:34 Local Registration: N122AT
Aircraft: Cessna 401B Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
On April 19, 2026, about 0834 eastern daylight time, a Cessna 401B, N122AT, was destroyed when it was involved in an accident near Land O’ Lakes, Florida. The commercial pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
Witnesses reported hearing the airplane flying at a low altitude, which drew their attention. One witness reported that the airplane was flying low and that the engine power sounded as though it was decreasing. The witness observed the airplane enter a descending left turn, followed by a brief right turn and a slight climb, before it “dropped out of the sky.” The witness then observed a large fireball followed by a plume of smoke.
Review of airport surveillance video showed the pilot arriving at the airport in a separate airplane, which he secured before conducting a preflight inspection of the accident airplane. The pilot was observed boarding the accident airplane and starting both engines; no noticeable anomalies were noted during engine start. The pilot taxied to the run-up area, where an engine run-up was performed. The airplane then taxied to runway 32 for departure.
The video showed the airplane begin its takeoff roll and climb normally after liftoff. The airplane was observed reaching an altitude of about 200 ft above ground level (agl) before exiting the camera’s field of view. A plume of smoke was observed rising shortly thereafter. The airplane came to rest in the backyard area of multiple residential homes. The fuselage was heavily damaged by impact forces and post-impact fire. The cockpit and cabin sections were largely consumed by fire, and the instrument panel was destroyed. Due to thermal damage, instrument indications were unreliable. All cockpit switches were destroyed by post-impact fire.
The main landing gear was observed in the retracted position. Flight control continuity was established to all flight control surfaces. Preliminary ADS-B data indicated that the airplane departed runway 32 at Tampa North Aero Park (X39), Tampa, Florida about 0834. During the initial climb, the airplane reached about 100 ft agl at an airspeed of about 81 knots. The airplane subsequently climbed to about 200 ft agl at an airspeed of about 86 knots and then slowed to about 79 knots. Track data was lost shortly thereafter. The total duration of the flight was about 30 seconds.
The airplane was retained for further examination.
FMI: www.ntsb.gov
NTSB Prelim: Cirrus Design Corp SR22T
At First Impact With The Ground Near Us 169 And 230th Road, The Wind Filled The Parachute And Dragged The Airplane Into A Fence Flipping The Airplane Upside Down
Location: Chanute, KS Accident Number: CEN26LA173
Date & Time: April 23, 2026, 14:45 Local Registration: N39VF
Aircraft: Cirrus Design Corp SR22T Injuries: 2 Minor
Flight Conducted Under: Part 91: General aviation - Business
On April 23, 2026, at about 1445 central daylight time, a Cirrus SR22T was substantially damaged when it was involved in an accident near Chanute, Kansas. The pilot and pilot-rated passenger sustained minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 business flight.
The airplane was enroute to Sikeston, Missouri, (SIK) when the engine made a loud “banging” noise. The pilot tried to divert to Chanute Martin Johnson Airport, CNU, but was unable to reach the airport. The engine lost all power, so the pilot declared an emergency with Air Traffic Control, Kansas City Center, and deployed the Cirrus Airframe Parachute System.
At first impact with the ground near US 169 and 230th road, the wind filled the parachute and dragged the airplane into a fence flipping the airplane upside down. The parachute continued to drag the airplane, with the pilot and passenger inside, through a farm field, and another fence, flipping the airplane right side up. The engine separated from the fuselage and the pilot was able to open the door and exit the airplane. As the airplane continued across the open field, the passenger exited to the right wing. A good Samaritan pulled off the road and tried to block the airplane with his truck. The airplane impacted the truck at which time the passenger fell off the wing. The empennage separated from the main fuselage as the wind continued to drag the airplane. The cabin and wings crossed US 169 and came to rest beside US 169 near 240th Road.
The airplane and engine were secured for further examination.
FMI: www.ntsb.gov
NTSB Final Report: Quad City Challenger
Pilot/Owner Reported That During Straight And Level Flight, He Felt A “Shudder” And Heard A “Thump” And The Airplane’s Engine Over Sped
Location: Van Burensburg, Illinois Accident Number: CEN26LA131
Date & Time: February 28, 2026, 16:00 Local Registration: UNREG
Aircraft: Quad City Challenger Aircraft Damage: Substantial
Defining Event: Part(s) separation from AC Injuries: 1 None
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot/owner reported that during straight and level flight, he felt a “shudder” and heard a “thump” and the airplane’s engine over sped. He executed a forced landing to a field, but the airplane’s right main landing gear separated from the airplane. The airplane came to rest on the remaining landing gear and the right wing. Postaccident examination revealed that the airplane’s pusher propeller had separated from the engine.
During the separation, the propeller struck the left wing, tearing the fabric covering and substantially damaging internal structure. The forced landing resulted in substantial damage to the fuselage lower longerons. Photographic evidence supplied by the pilot showed that the threaded portion of the 6 bolts that retained the propeller were still in the engine propeller hub. The propeller and the unthreaded portion of the propeller bolts were not recovered.
The pilot reported that other than the propeller separation, there were no preexisting mechanical problems with the airplane. He noted that the accident could have been prevented by performing a better inspection under the propeller hub, noting that the propeller bolts are not visible during daily inspections.
The airplane was not registered, and the pilot did not hold a Federal Aviation Administration issued pilot certificate. He reported that he thought the operation of the airplane was covered under Title 14 Code of Federal Regulations (CFR) Part 103 – Ultralight Vehicles. 14 CFR 103 details the operation of ultralight vehicles that do not require a pilot certificate, a medical certificate, or registration of the vehicle. The vehicle requirements include an empty weight of less than 254 pounds, a fuel capacity not exceeding 5 gallons, a maximum level flight speed of 55 kts., and a stall speed of no more than 24 kts. Although the airplane was not weighed following the accident, research indicated that the accident airplane may have achieved all the requirements, except the fuel limitation. The accident airplane was equipped with a 10-gallon fuel tank. As such, the airplane should have been registered, and the pilot should have been certificated.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- Propeller separation due to failure of the propeller attachment bolts.
FMI: www.ntsb.gov
Today in History
30 Years ago today: On 11 May 1996 ValuJet Airlines flight 592, a DC-9-30, crashed in the Everglades, FL, USA, following an in-flight fire, killing all 110 occupants.
| Date: | Saturday 11 May 1996 |
| Time: | 14:13 |
| Type: | McDonnell Douglas DC-9-32 |
| Owner/operator: | ValuJet Airlines |
| Registration: | N904VJ |
| MSN: | 47377/496 |
| Year of manufacture: | 1969 |
| Total airframe hrs: | 68395 hours |
| Cycles: | 80663 flights |
| Engine model: | P&W JT8D-9A |
| Fatalities: | Fatalities: 110 / Occupants: 110 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Everglades, FL - United States of America |
| Phase: | En route |
| Nature: | Passenger - Scheduled |
| Departure airport: | Miami International Airport, FL (MIA/KMIA) |
| Destination airport: | Atlanta-William B. Hartsfield International Airport, GA (ATL/KATL) |
| Investigating agency: | NTSB |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
ValuJet Airlines flight 592, a DC-9-30, crashed in the Everglades, FL, USA, following an in-flight fire, killing all 110 occupants.
Flight 592 was a scheduled flight from Miami (MIA) to Atlanta (ATL). The inbound flight had been delayed and arrived at Miami at 13:10. Flight 592 had been scheduled to depart at 13:00. The cruising altitude was to be flight level 350 with an estimated time en route of 1 hour 32 minutes. The DC-9 was loaded with 4,109 pounds of cargo (baggage, mail, and company-owned material (COMAT)). The COMAT consisted of two main tires and wheels, a nose tire and wheel, and five boxes that were described as "Oxy Cannisters -‘Empty.’" This cargo was loaded in the forward cargo compartment.
Flight 592 was pushed back from the gate shortly before 13:40. The DC-9 then taxied to runway 09L. At 14:03:24, ATC cleared the flight for takeoff and the flightcrew acknowledged the clearance. At 14:04:24, the flightcrew was instructed by ATC to contact the north departure controller. At 1404:32, the first officer made initial radio contact with the departure controller, advising that the airplane was climbing to 5,000 feet. Four seconds later, the departure controller advised flight 592 to climb and maintain 7,000 feet. The first officer acknowledged the transmission. At 14:07:22, the departure controller instructed flight 592 to "turn left heading three zero zero join the WINCO transition climb and maintain one six thousand," which was acknowledged. At 14:10:03, the flight crew heard a sound, after which the captain remarked, "What was that?" At that moment, the airplane was at 10,634 feet msl, 260 knots indicated airspeed (KIAS), and both engine pressure ratios (EPRs) were 1.84. At 14:10:15, the captain stated, "We got some electrical problem," followed 5 seconds later with, "WeÂ’re losing everything." At 14:10:21, the departure controller advised flight 592 to contact Miami on frequency 132.45 mHz. At 14:10:22, the captain stated, "We need, we need to go back to Miami," followed 3 seconds later by shouts in the background of "fire, fire, fire, fire." At 14:10:27, the CVR recorded a male voice saying, "WeÂ’re on fire, weÂ’re on fire." At 14:10:28, the controller again instructed flight 592 to contact Miami Center. At 14:10:31, the first officer radioed that the flight needed an immediate return to Miami. The controller replied, "Critter five ninety two uh roger turn left heading two seven zero descend and maintain seven thousand." The first officer acknowledged the heading and altitude. The peak altitude reached was 10,879 feet msl at 14:10:31, and about 10 seconds a wings-level descent started. Shouting in the cabin subsided. The controller then queried flight 592 about the nature of the problem. The captain stated "fire" and the first officer replied, "uh smoke in the cockp... smoke in the cabin." The controller responded, "roger" and instructed flight 592, when able, to turn left to a heading of two five zero and to descend and maintain 5,000 feet. At 14:11:12, a flight attendant was heard shouting, "completely on fire." The DC-9 began to change heading to a southerly direction and at 14:11:26, the north departure controller advised the controller at Miami Center that flight 592 was returning to Miami with an emergency. At 14:11:37, the first officer transmitted that they needed the closest available airport. At 1411:41, the controller replied, "Critter five ninety two theyÂ’re gonna be standing (unintelligible) standing by for you, you can plan runway one two when able direct to Dolphin [a navaid] now." At 14:11:46, the first officer responded that the flight needed radar vectors. At 14:11:49, the controller instructed flight 592 to turn left heading one four zero. The first officer acknowledged the transmission. At 14:12:45, the controller transmitted, "Critter five ninety two keep the turn around heading uh one two zero." There was no response from the flightcrew. The last recorded FDR data showed the airplane at 7,200 feet msl, at a speed of 260 KIAS, and on a heading of 218 degrees. At 14:12:48, the FDR stopped recording data. The airplaneÂ’s radar transponder continued to function; thus, airplane position and altitude data were recorded by ATC after the FDR stopped. At 14:13:18, the departure controller instructed, "Critter five ninety two you can uh turn left heading one zero zero and join the runway one two localizer at Miami." Again there was no response. At 14:13:27, the controller instructed flight 592 to descend and maintain 3,000 feet. At 1413:37, an unintelligible transmission was intermingled with a transmission from another airplane. No further radio transmissions were received from flight 592. At 14:13:43, the departure controller advised flight 592, "Opa Locka airportÂ’s about 12 oÂ’clock at 15 miles." The accident occurred at 14:13:42. Ground scars and wreckage scatter indicated that the airplane crashed into the Everglades in a right wing down, nose down attitude.
PROBABLE CAUSE: "The National Transportation Safety Board determines that the probable causes of the accident, resulting in a fire in the Class D cargo compartment from the actuation of one or more oxygen generators improperly carried as cargo, were: (1) the failure of SabreTech to properly prepare, package, identify, and track unexpended chemical oxygen generators before presenting them to ValuJet for carriage; (2) the failure of ValuJet to properly oversee its contract maintenance program to ensure compliance with maintenance, maintenance training, and hazardous materials requirements and practices; and (3) the failure of Federal Aviation Administration (FAA) to require smoke detection and fire suppression systems in Class D cargo compartments.
Contributing to the accident was the failure of the FAA to adequately monitor ValuJet's heavy maintenance program and responsibilities, including ValuJet's oversight of its contractors, and SabreTech's repair station certificate; the failure of the FAA to adequately respond to prior chemical oxygen generator fires with programs to address the potential hazards; and the failure of ValuJet to ensure that both ValuJet and contract maintenance employees were aware of the carrier's no-carry hazardous materials policy and had received appropriate hazardous materials training." (NTSB/AAR-97/06)
