We start the week with these stories...
Be safe out there!
Tom
--
Semi hauling jet fuel rolls over, catches fire; SR-56 closed in both directions in Iron County
Written by E. George Goold
State Route 56 remained closed in both east and west
directions near mile marker 19 after a semi truck hauling jet fuel rolled over and caught fire on Saturday afternoon.
Utah Highway Patrol Trooper Kyley Tobler told St. George News that the driver of the semi was on the scene when first responders arrived.
“The driver was transported to a local hospital with minor injuries,” Tobler said. “He was walking and talking so it wasn’t as bad as it could have been.”
“The fire is still burning,” Tobler said at 4 p.m. “He was hauling 3,600 pounds of jet fuel.”
Crews were to remain on scene and the road was to remain closed until the fire is completely out and clean up could commence, Tobler said.
As seen in the video provided to St. George News by Enterprise Fire Department, heavy black smoke billowed from the overturned semi and a fire grew rapidly, burning bright orange.
Mile marker 19 is between the towns of Newcastle and Beryl Junction.
Tobler said no other injuries were reported and she did not have an estimate for when SR-56 might reopen.
“No cause has been determined,” Tobler said. “That is still under investigation.”
St. George News will update this story with any future developments.
This report is based on information by first responders and may not include the full scope of the investigation.
https://www.stgeorgeutah.com/news/semi-hauling-jet-fuel-rolls-over-catches-fire-sr-56-closed-in-both-directions-in/article_aa3661fc-3fac-41d3-beb8-8d4a0b7c4d64.html
Two Oklahoma men killed after small plane crashes near Waterloo in early-morning search
A father and son from Oklahoma died after their aircraft went down in a tree line behind the Columbia Quarry near T Road south of Waterloo. Monroe County officials and federal investigators are continuing an inquiry into what led to the crash.
By Grace Kowalski
Key takeaways
- A small plane carrying a 48-year-old pilot and his 22-year-old son crashed south of Waterloo, Illinois; both died.
- Wreckage was found just before 8 a.m. near the Columbia Quarry after a search hampered by rain and low visibility.
- The FAA and NTSB are leading the investigation; preliminary data show the aircraft entered a descending spiral after turning, and radar contact was lost.
MONROE COUNTY, Ill. — An Oklahoma father and son were killed when their small plane crashed in rural Monroe County early Friday, ending an hourslong search that began after calls of a possible aircraft accident just after 2:30 a.m., county investigators said.
Where and when the wreckage was found 
Emergency crews were dispatched to the area south of Waterloo shortly after 2:30 a.m. Friday following reports of a possible plane crash. Adverse weather — including rain, low cloud cover and poor visibility — complicated early search efforts, officials said.
Responders located the wreckage near a tree line behind the Columbia Quarry near T Road just before 8 a.m., bringing an end to an hourslong multi-agency effort to find the aircraft.
Who died and where the flight departed
Investigators identified the victims as a 48-year-old man from Oklahoma, the pilot, and his 22-year-old son. Officials said the aircraft had departed from St. Louis Regional Airport in Bethalto, Illinois, and was bound for Siloam Springs Municipal Airport in Arkansas.
Weather, radar data and the ongoing investigation
Preliminary flight data indicate the plane took off into an area of developing severe weather. Local investigators said the aircraft appeared to begin a turn, possibly to avoid the storm, before entering what officials described as a descending spiral. Radar contact was then lost.
The Federal Aviation Administration and the National Transportation Safety Board are leading the formal investigation. Monroe County authorities have said the cause of the crash has not yet been determined and the inquiry is ongoing.
Local response and rescue effort
Because of limited visibility and precipitation, the search included multiple local agencies. Officials said responders who took part in the operation included local law enforcement, volunteer and municipal firefighters, emergency medical services and emergency management personnel.
- Initial dispatch: just after 2:30 a.m. Friday.
- Wreckage located: just before 8 a.m., tree line behind Columbia Quarry near T Road.
- Departure airport: St. Louis Regional Airport in Bethalto.
- Destination: Siloam Springs Municipal Airport, Arkansas.
- Federal agencies leading investigation: FAA and NTSB.
| Item | Detail |
| Dispatch time | Just after 2:30 a.m., Friday |
| Wreckage found | Just before 8 a.m., Friday |
| Victims | 48-year-old pilot; 22-year-old son (both from Oklahoma) |
| Origin / Destination | St. Louis Regional (Bethalto) → Siloam Springs Municipal (Ark.) |
Officials said they later learned the pilot and his son had attended a St. Louis Cardinals baseball game before beginning their trip home. Beyond the timeline and the preliminary flight data, authorities have not released additional information about the identities of the victims or other details of the flight.
This is an active investigation. The FAA and NTSB will continue to examine radar and flight data, wreckage and other evidence to determine probable cause. Monroe County authorities asked anyone with information to contact the sheriff’s department through their established channels.
For residents in the area and those who may have observed anything overnight, local officials advise preserving any potential evidence — such as photos, video or dashcam footage — and offering it to investigators if requested.
Grace Kowalski is the Illinois correspondent for News Block.
https://news-block.org/two-oklahoma-men-killed-after-small-plane-crashes-near-waterloo-in-early-morning-search
Small plane makes emergency water landing near Honeymoon Island State Park: DFR
Dunedin Fire Rescue said all occupants safely reached shore with minor injuries after the aircraft went down offshore.
By: Anthony Romano
DUNEDIN, Fla. — A small aircraft made an emergency landing in the water near Honeymoon Island State Park on Sunday afternoon, according to Dunedin Fire Rescue (DFR). 
Crews responded around 12:38 p.m. to reports of an aircraft emergency near 1 Causeway Boulevard. Officials said the plane experienced an in-flight emergency before coming to rest about 25 yards offshore, according to a news release.
Both occupants safely exited the aircraft and made it to shore. Fire and EMS crews evaluated the occupants, who suffered only minor injuries, DFR said.
The Pinellas County Sheriff's Office said its dive team noticed a small fuel leak into the water from the aircraft.
Multiple agencies responded to assist, including the Pinellas County Sheriff’s Office, Florida Fish and Wildlife Conservation Commission, U.S. Coast Guard and Florida State Parks, per the release.
As of Sunday evening, the plane has been removed from the water.
The incident remains under investigation.
https://www.tampabay28.com/news/region-pinellas/small-plane-makes-emergency-water-landing-near-honeymoon-island-state-park-dfr
10 killed after plane crashes in Bahamas, Flamingo Air flights grounded, PM Davis expresses grief
Edited By: Manmath Nayak
Bahamian Prime Minister Philip Brave Davis expressed grief and initially said that one person survived, but he later confirmed in a press conference that the person died from their injuries. The victims have not been publicly identified. 
Nassau:
A small plane crashed in the Bahamas on Friday, killing 10 people and prompting the government to temporarily ground Flamingo Air flights. The deadly incident happened in North Andros, located in waters just west of Nassau, the archipelago's capital.
Prime Minister Philip Brave Davis expresses grief
Bahamian Prime Minister Philip Brave Davis expressed grief and initially said that one person survived, but he later confirmed in a press conference that the person died from their injuries. The victims have not been publicly identified.
"We gather beneath a cloud of great sorrow," he said, noting that people were celebrating the Bahamas' 53rd independence anniversary. "It has become a day of mourning. ... To every family that has received the devastating news, that someone they love will not be coming home, we offer our deepest condolences."
Here's what Bahamian Aircraft Accident Investigation Authority said
The Bahamian Aircraft Accident Investigation Authority said in a statement that the plane had departed Lynden Pindling International Airport in Nassau and was headed to San Andros when it crashed. It identified the plane as a Cessna 402 aircraft registered in the Bahamas.
The Ministry of Energy, Utilities and Aviation said in a statement that the suspension of Flamingo Air's air operator certificate is only a precautionary safety measure as officials investigate the cause of the crash. The ministry said the suspension is a result of two safety incidents that happened Friday.
During the press conference, Energy, Utilities and Aviation Minister JoBeth Coleby-Davis said the first incident occurred earlier Friday involving a Flamingo Air plane. She said it was en route to Mayaguana when the pilot reported a concern and turned back to Nassau. After the plane landed and the passengers deboarded, the plane caught fire, she said. That incident also is under investigation.
Another small plane crashed in 2014
In 2014, another small plane crashed on approach to the island of Grand Bahama, killing all 9 people on board, the government of the Bahamas said. The Lear 36 Executive Jet had taken off from the Bahamian capital of Nassau and crashed while attempting to land around 5 pm local time in Freeport, according to a statement from the Ministry of Transport and Aviation.
"The Department of Civil Aviation has been advised unofficially that the aircraft was destroyed and that there were no survivors," the ministry said. Names of the victims were not immediately available. The cause of the crash has not yet been determined though there had been heavy rain across the region. Police and fire authorities were on scene and a full investigation would begin at daylight on Monday.
The crash occurred as people were gathering in Grand Bahama for an annual Christian leadership conference. The Bahamas Tribune newspaper reported that Myles Munroe, a prominent Bahamian minister who organized the event, was among those killed, along with several other people who were in his delegation.
https://www.indiatvnews.com/news/world/10-killed-after-plane-crashes-in-bahamas-flamingo-air-flights-grounded-pm-davis-expresses-grief-2026-07-11-1047881
NTSB investigating helicopter crash near Marlinton, West Virginia that killed 57-year-old man
10 News Digital Team
MARLINTON, WV – Update:
The West Virginia State Police announced that it had responded to the scene of the downed aircraft near Marlinton on Friday.
Troopers from Elkins and Marlinton Detachments, along with the Pocahontas County Office of Emergency Management and the Marlinton Volunteer Fire Department, responded to the scene.
Upon arrival, it was determined that a privately owned Sikorsky S-76D helicopter, tail number N93RT, had crashed near the 6000 block of Huntersville Road in Marlinton.
According to WVSP, the aircraft was owned by Waco Oil and Gas Co., Inc and was being operated by 57-year-old Leo Basile of Arthurdale, West Virginia.
The investigation determined that Basile was the sole occupant of the aircraft and was pronounced dead at the scene.
The Federal Aviation Administration has been notified and is coordinating with the appropriate investigative agencies to determine the cause of the crash.
Original:
Federal investigators are looking into the cause of a helicopter crash that happened Friday morning near Marlinton, West Virginia.
According to the National Transportation Safety Board, the crash involved a Sikorsky S-76D helicopter and was reported at approximately 7:47 a.m. EDT.
The NTSB said three investigators are traveling to the crash site to begin documenting the wreckage before it is moved to a secure facility for further examination.
Anyone with information that could assist investigators is asked to contact the NTSB at witness@ntsb.gov.
The NTSB said it is not responsible for releasing the identities of those involved in the crash or information about injuries or fatalities. That information will be provided by local authorities.
A preliminary report is expected within 30 days. The report will summarize facts gathered during the initial phase of the investigation but will not identify the cause of the crash. A final report, including the probable cause and any contributing factors, is expected within 12 to 24 months.
The preliminary report will be available through the NTSB Daily Publication Dashboard once it is released.
NTSB investigating helicopter crash near Marlinton, West Virginia that killed 57-year-old man
10 News Digital Team
MARLINTON, WV – Update:
The West Virginia State Police announced that it had responded to the scene of the downed aircraft near Marlinton on Friday.
Troopers from Elkins and Marlinton Detachments, along with the Pocahontas County Office of Emergency Management and the Marlinton Volunteer Fire Department, responded to the scene.
Upon arrival, it was determined that a privately owned Sikorsky S-76D helicopter, tail number N93RT, had crashed near the 6000 block of Huntersville Road in Marlinton.
According to WVSP, the aircraft was owned by Waco Oil and Gas Co., Inc and was being operated by 57-year-old Leo Basile of Arthurdale, West Virginia.
The investigation determined that Basile was the sole occupant of the aircraft and was pronounced dead at the scene.
The Federal Aviation Administration has been notified and is coordinating with the appropriate investigative agencies to determine the cause of the crash.
Original:
Federal investigators are looking into the cause of a helicopter crash that happened Friday morning near Marlinton, West Virginia.
According to the National Transportation Safety Board, the crash involved a Sikorsky S-76D helicopter and was reported at approximately 7:47 a.m. EDT.
The NTSB said three investigators are traveling to the crash site to begin documenting the wreckage before it is moved to a secure facility for further examination.
Anyone with information that could assist investigators is asked to contact the NTSB at witness@ntsb.gov.
The NTSB said it is not responsible for releasing the identities of those involved in the crash or information about injuries or fatalities. That information will be provided by local authorities.
A preliminary report is expected within 30 days. The report will summarize facts gathered during the initial phase of the investigation but will not identify the cause of the crash. A final report, including the probable cause and any contributing factors, is expected within 12 to 24 months.
The preliminary report will be available through the NTSB Daily Publication Dashboard once it is released.
NTSB Preliminary Report On NetJets Cessna Down On Laredo Highway
Report Says Crew Reported Low Fuel Pressure And Unusual Vibration
A preliminary report from the National Transportation Safety Board (NTSB) says the pilots of a Textron Aviation 680A, registration N523QS operated by NetJets, was en route from Los Cabos, Mexico, to Austin when the crew declared an emergency and diverted to Laredo International Airport. 
According to the flight crew, early in the flight, they noticed an unusual vibration, which they had not experienced before. They contacted the NetJets Flight Operations Duty Manager (FODM) via telephone and during that initial conversation, the flight crew described the vibration as “a low frequency vibration and a humming noise… it sounds like a fan is on… you can feel it in the dashboard…it was on steady during the climb, but it is gone now.”
After further discussion with the maintenance controller and FODM, it was determined that the flight could safely proceed to its planned destination and write-up the vibration once the flight was completed.
As the airplane approached the U.S. and Mexico border, the flight crew received a message which indicated that the right fuel system had low fuel pressure. They then received an electrical transformer rectifier unit failure message and declared an emergency.
They contacted Houston Air Route Traffic Control and reported a generator failure and “multiple other failures” issues including “fuel level low.” They requested to divert to Laredo International Airport (LRD), Laredo, Texas.
While the plane was on final to Runway 36L the right engine flamed out, followed a few seconds later by the left engine. The first officer asked Laredo air traffic control if there were any open fields nearby and were told “it’s just going to be the main highway, and that’s just about it.”
The flight crew maneuvered the airplane to touch down on the northbound lanes of the Bob Bullock Loop, about one mile southeast of the airport. As the airplane touched down in the northbound lanes of traffic, it sheared off several light poles, struck a vehicle, and came to rest straddling the right-hand edge of an overpass.
Six people were aboard the aircraft, all male, according to Laredo police. The passenger who died was identified by police as Josh Baer, 50, founder and CEO of Austin-based tech company Capital Factory. Three teenagers were also on the plane: a 17-year-old, a 16-year-old, and a second 16-year-old who was related to Baer. They received minor injuries. The captain received serious injuries, the first officer received minor injuries. 
The NTSB examined the plane in a hangar and said further examination revealed that the right engine fuel pressure switch was found separated from the fuel tube assembly and the fuel tube assembly was fractured adjacent to the weld joint for the attachment tube leading to the fuel pressure switch. Multiple P-clamps on the fuel tube assembly were also found fractured.
The starter generator shaft was found bent, the cooling fan was fractured, and multiple cooling fan blades and ball bearings were found when the generator was removed. The cooling fan shroud also contained circumferential scoring marks.
No official cause of the crash was listed.
FMI: www.ntsb.gov
NTSB Final Report: Quicksilver GT-400
Pilot Reported That He Later Learned He Did Not Have Sufficient Flaps Extended For The Landing Configuration
Location: Chula Vista, California Accident Number: WPR26LA148
Date & Time: March 23, 2026, 15:30 Local Registration: N120LF
Aircraft: Quicksilver GT-400 Aircraft Damage: Substantial
Defining Event: Hard landing Injuries: 1 None
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot was on a local flight in the airport traffic pattern in an airplane he had recently purchased. During a landing attempt the airplane landed hard and bounced at which time the pilot applied full power to perform a go-around. He then elected to abort the go-around and land after he determined the airplane would not clear trees at the end of the runway. The airplane overran the runway end and impacted brush, resulting in substantial damage to both wings.
The pilot reported that he later learned he did not have sufficient flaps extended for the landing configuration.
The pilot reported there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s improper landing flare, which resulted in a bounced landing and a subsequent runway excursion.
FMI: www.ntsb.gov
NTSB Final Report: Cameron Balloons US C-80
During Touchdown, The Basket Bounced And Was Dragged Across The Ground
Location: Rio Rancho, New Mexico Accident Number: WPR26LA176
Date & Time: May 3, 2026, 08:15 Local Registration: N4022X
Aircraft: Cameron Balloons US C-80 Aircraft Damage: None
Defining Event: Miscellaneous/other Injuries: 1 Serious, 1 None
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot of the balloon reported that he and the passenger, who had recently purchased the balloon, were conducting a local flight. Before departure, he briefed the passenger on proper landing posture and hand placement down low and not on the uprights. The takeoff and enroute phase of the flight were unremarkable.
While on final approach to land, the pilot conducted a steep approach and demonstrated ground-tracking maneuvers before the final touchdown. During touchdown, the basket bounced and was dragged across the ground. The passenger was holding onto a basket upright during one of the bounces. Subsequently, the upright fractured and the passenger sustained a serious injury.
The pilot reported there were no preaccident mechanical malfunctions or failures with the balloon that would have precluded normal operation.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The passenger’s improper hand placement on the basket upright during landing, which resulted in injury when the upright fractured during the basket’s bounce and drag sequence.
FMI: www.ntsb.gov
NTSB Final Report: Autogyro Cavalon
A Wind Gust Pushed The Gyrocopter To The Right And The Right Main Landing Gear Wheel “Came Down Hard.”
Location: Palo Alto, California Accident Number: WPR26LA194
Date & Time: May 13, 2026, 15:35 Local Registration: N40CT
Aircraft: Autogyro Cavalon Aircraft Damage: Substantial
Defining Event: Hard landing Injuries: 1 Minor
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot of the gyrocopter reported that during his approach to land on runway 31, the reported wind information indicated a gusting crosswind from the left. On final approach the gyrocopter required left stick and right rudder inputs to remain lined up with the runway. The pilot queried the air traffic control tower for the current wind conditions prior to landing, and was told 250° at 13 knots, gusting to 20 knots. The pilot intended to touch down with the left main landing gear wheel first, however, a wind gust pushed the gyrocopter to the right and the right main landing gear wheel “came down hard.” The pilot released the crosswind correction input and moved the control stick to the center, and the gyrocopter continued toward the right side of the runway. The gyrocopter subsequently exited the right side of the runway, rolled over and came to rest on its right side. The fuselage and main rotor driveshaft were substantially damaged.
The pilot reported that there were no preaccident mechanical malfunctions or failures that would have precluded normal operation.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s failure to maintain directional control during the landing roll, in gusting crosswind conditions.
FMI: www.ntsb.gov
Today in History
15 Years ago today: On 13 July 2011 A NOAR Let L-410 passenger plane, registered PR-NOB, was destroyed in an accident near Recife-Guararapes International Airport, PE (REC), Brazil. All 14 passengers and two crew members were killed.
| Date: | Wednesday 13 July 2011 |
| Time: | 06:54 |
| Type: | Let L-410UVP-E20 |
| Owner/operator: | NOAR Linhas Aéreas |
| Registration: | PR-NOB |
| MSN: | 2722 |
| Year of manufacture: | 2010 |
| Total airframe hrs: | 2126 hours |
| Cycles: | 3033 flights |
| Engine model: | Walter M-601E |
| Fatalities: | Fatalities: 16 / Occupants: 16 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | 1,7 km SSE of Recife-Guararapes International Airport, PE (REC) - Brazil |
| Phase: | Initial climb |
| Nature: | Passenger - Scheduled |
| Departure airport: | Recife-Guararapes International Airport, PE (REC/SBRF) |
| Destination airport: | Natal Air Force Base, RN (SBNT) |
| Investigating agency: | CENIPA |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
A NOAR Let L-410 passenger plane, registered PR-NOB, was destroyed in an accident near Recife-Guararapes International Airport, PE (REC), Brazil. All 14 passengers and two crew members were killed.
The airplane operated on NOAR Linhas Aéreas Flight 4896 from Recife (REC) to Mossoró (MVF) with an en route stop at Natal (NAT). The airplane had taken off from runway 18 at Recife at 06:51.
During the takeoff briefing, the captain said that he would consider the possibility of landing on the runway, if a failure occurred after V1 (decision speed), with sufficient runway and the landing gear still not retracted.
He also said that, if a failure occurred after V1 and with the landing gear retracted, he would proceed with the flight, while the copilot would be in charge of monitoring the instruments and complementing the emergency procedures after 400ft AGL. He informed that, in such case, the turns would be made towards the "good engine" side.
During the takeoff, three seconds after the captain requested retraction of the landing gear, a sound was heard from the engines.
Despite the captain's request to retract the landing gear, his request was only complied with 50 seconds later, after the fourth time he repeated it.
After verifying the engine failure occurrence, the copilot asked the captain to "abort takeoff" three times, adding that the aircraft had lost power. The captain proceeded with the departure, saying that there was not enough space to abort takeoff.
The captain, then, told the copilot to request landing on runway "thirty", repeating this request twice, without taking into account that Recife Airport runway has the thresholds 18 and 36. The copilot, however, informed the Tower controller that the aircraft would proceed for a landing on runway 36.
Shortly after this message, the copilot asked the captain to "lower the aircraft nose". In his reply, the captain asked the copilot to take it easy, and the copilot agreed: "I know, we are at 400ft, let's fly!".
Then, there was a significant change in the cockpit background noise, with the captain telling the copilot to feather the propellers of engine number 1.
The captain told the copilot to call the Tower, and the copilot asked what his message to ATC should be. The captain instructed him to tell ATC that they were in emergency.
The copilot's answer to the captain was: "We are in emergency. We are cleared to land on runway 36, let's go".
Then, the alerts "Don't sink! Don't sink!" and "Too low, terrain" were heard several times.
At 06:52:45, the captain asked the copilot to feather the left engine propeller blades, and the copilot answered by saying that the propeller blades had already been feathered.
At 06:52:52, the copilot asked the captain to turn towards the aerodrome. The captain answered that he was already doing so. Shortly after, at 06:53:02, the stall alert went off.
The copilot then said "eighty-one, lower the nose", and then the alerts "Don't sink! Don't sink!" and "Too low, terrain!" were heard.
At 06:53:22, the copilot uttered "one hundred twenty feet" and then a stall alert was heard.
The copilot asked the captain to 'hold the power', and the captain said that 'it was in full power'.
Then, the copilot asked the captain not to hold the nose too much to keep the aircraft from stalling.
He then asked the captain whether they would land on the beach, and received a firm "no" as an answer.
At 06:53:43, the copilot commented to the captain that they were at a hundred twenty feet, and that there was not sufficient height to proceed to the runway, suggesting that they should land on a sand strip on the beach.
The captain replied that he would not land on the beach, and informed that they would land in the "field", instead.
At 06:53:56, the copilot radioed: "NOAR 4-8-9-6 is... it is going to make an emergency landing on the beach...it is not possible to reach the runway... land here in the sand... land in the sand that does notÂ…".
Then, the stall alert went off.
The captain, anew, told the copilot that they would not land in the sand, and the copilot replied that they would fall on top of the buildings. From this moment on, the stall alert continued being heard for 19 seconds up to the time the stall occurred, occasionally intercalated with the alerts "Don't sink! Don't sink!" and "Too low, terrain!"
At 06:54:12, the copilot asked the PIC to "please" land on the beach, to which the captain rudely answered that he would not do that.
The copilot insisted, saying that they were not able to reach the runway, and the PIC said: "It's OK! Leave it to me!"
At 06:54:25, the copilot made a comment to the captain that they were stalling and repeated the comment.
The nose was pitching up until the aircraft stalled, impacting a field close to a road. A fire erupted. The airplane came down in a vacant lot near the beach, located 1700 m from the runway threshold.
Contributing factors
1. Human Factor
1.1 Medical aspect
a) Anxiety - undetermined
The perception of the danger, especially on the part of the copilot, affected the communication, and may have inhibited a more assertive posture, which might have led to an emergency landing on the beach and minimize the consequences of the accident.
1.2 Psychological aspect
1.2.1 Individual information
a) Attitude - undetermined
The operational actions taken in face of the emergency may have resulted from the high level of the PICÂ’s self-confidence obtained in his years of experience in aviation, as well as from his resistance to accept opinions that were different from his own.
b) Emotional state - undetermined
From the CVR data, it is possible to observe an accentuated level of anxiety and tension in face of the abnormal situation. These components may have influenced the judgment of the conditions affecting the operation of the aircraft.
c) Decision making process - a contributor
The PICÂ’s insistence on proceeding to runway 36 after the onset of the emergency, even after the copilotÂ’s realization that they were no longer able to reach the aerodrome, reflects an inappropriate judgment of the operational information presented.
d) Stress evidence - undetermined
The unexpected emergency situation during the takeoff and the lack of preparedness to deal with it may have generated a level of stress in the crew, affecting their operational response.
1.2.2 Psychosocial information
a) Interpersonal relationship - undetermined
The history of divergences involving the two pilots possibly hindered the exchange of information between them, creating a barrier for dealing with the adverse situation.
b) Team dynamics - a contributor
The presence of diverging ideas in relation to the actions to be taken and the way they were treated, revealed cockpit integration and coordination problems that made it difficult to choose the best option for a safe landing when the aircraft could no longer reach
the aerodrome.
c) Work-group culture - undetermined
The company was informally divided into two groups, whose interaction was difficult. It is possible that this interaction difficulty was reflected in cabin management during the emergency, since this flight had a crewmember from each group.
1.2.3 Organizational information
a) Training - a contributor
The failures that occurred in the companyÂ’s training process affected the performance of the crew, since they did not have a conditioned behavior regarding the adoption of safe actions in response to the emergency.
b) Organizational culture - a contributor
The actions taken by the company indicate informalities that resulted in incomplete operational training and in acts that compromised safety.
1.3 Operational aspect
1.3.1 Concerning the operation of the aircraft
a) Application of flight controls - a contributor
According to the FDR data, the pedal was not applied in a way that would allow a deflection of the rudder sufficient to maintain the coordination of the aircraft from a certain moment of the flight with asymmetric power.
The drift values obtained on account of the inadequate application of the pedal penalized the aircraft performance, rendering it impossible to maintain a climb gradient or even a leveled flight.
In the final phase of the flight, even with the decrease of the speed to values below the VMCA, in the midst of the continuous sound of the stall alert and repeated requests by the copilot to not "hold the nose so as not to stall", the PIC continued actuating in the pitch control until the aircraft reached a longitudinal attitude of 18° and stalled.
b) Cockpit coordination - a contributor
The delay in retracting the landing gear after the first request made by the PIC, the command of the PIC to feather the propeller blades when they had already been feathered, and the request made by the copilot asking the PIC to turn towards the airport when the aircraft was already turning, were indications that the flow of tasks in the cockpit was not well coordinated.
