Skip to content

Today is Monday the 1st of June, 2026

We kick off the month of June with these stories from over the weekend...

Be safe out there!

Tom

--

2 injured when small plane crashes in Pembroke Pines near South Florida State Hospital, officials say

By Steven Yablonski, Peter D'Oench

Two people were rushed to a Broward hospital late Friday morning after a small plane they were on crashed into a Pembroke Pines neighborhood, according to officials.

According to Pembroke Pines Fire Rescue, emergency crews responded to reports of a single-engine Cessna C172P airplane that crashed just north of the main building at South Florida State Hospital just before 11:30 a.m.

South Florida State Hospital is adjacent to North Perry Airport.

According to information provided by the Federal Aviation Administration, the plane crashed shortly after departing from North Perry Airport.

Pembroke Pines Fire Rescue said that when emergency crews arrived at the scene, they found two injured adults, and they were rushed to Memorial Regional Hospital in Hollywood as trauma patients.

However, in a post on X, the Pembroke Pines Police Department said that the injured adults were "conscious and breathing" and that no other injuries were reported.

Emergency officials said that a small fuel leak on the plane was also reported, and it was mitigated by Pembroke Pines fire crews.

The Federal Aviation Administration told CBS News Miami that it is investigating the crash and may be releasing a preliminary report on Saturday.

Pembroke Pines Mayor Angelo Castillo told CBS News Miami that the plane took off westbound and shortly after it experienced engine failure. "The plane took off westbound, and shortly after it took off, it experienced engine failure and went to make a turn, probably to try to go back to the airport, and didn't have altitude and hit a tree and went into a ditch and flipped over," Castillo said.

"It's a good thing for them because it was headed for a building that houses patients who receive medical and mental health care," he added. "The people on board were complaining of back pain. The plane did not ignite".

Castillo criticized the continued crashes at the facility. "Here we go again with North Perry Airport," he said. "It is a routine thing in Pembroke Pines where these crashes continue to happen".

He said there have been about 40 crashes in the past five years involving planes from the airport and its 11 flight schools.

The plane that crashed was from Blue Sky Aviation and is run by Pembroke Pines City Commissioner Jay Schwartz, who told CBS News Miami that they were looking into how the accident happened.

Castillo said it was not known if it was the student or the flight instructor flying the plane. He credited a good Samaritan for helping the crash victims and said he would like to meet and thank him.

He also noted the county was in the process of hiring a consultant to look at air quality and air safety at the airport.

"What can they do to make the air safer in this community that is waiting for that to happen?" he said. "If they can't make it safer, they need to close it down and put the planes somewhere else where they don't threaten people".

CBS News Miami also reached out to Broward Aviation, which runs the airport, and they provided a statement that said in part:

"As a Broward County-owned and operated airport, safety is a top priority at HWO. Earlier in May, the general aviation facility passed its Florida Department of Transportation (FDOT) annual inspection with zero discrepancy (no safety, regulatory, or operational violations) for the 26th consecutive year.

FDOT's inspection, which is required to maintain the airport's operating license, includes a review of airfield markings and signs, runway/taxiway lights, approach slopes, and safety areas. While the County will not speculate as to the cause or causes of this accident, we will be cooperating with the authorities as they conduct their investigation."

https://www.cbsnews.com/miami/news/pembroke-pines-plane-crash-may-29-2026/

Pilot hospitalized after coming up short of the runway at Sanderson Field in Shelton

KIRO 7 News Staff

A 72-year-old pilot was taken to the hospital after an airplane crash at Sanderson Field in Shelton.

According to the Mason County Sheriff’s Office, the aircraft came up short of the runway on approach.

The pilot was the only one inside the plane at the time of the crash.

No word on his condition.

There were no reports of fire associated with the crash.

Pictures from the incident show the small aircraft on its nose in the grass, with the turbine ripped off.

Fire personnel, law enforcement, and the Federal Aviation Administration (FAA) are on scene.

https://www.yahoo.com/news/us/articles/pilot-hospitalized-coming-short-runway-215744507.html

Plane Crash Injures 1 at Double Eagle Airport

By newsdesk

Albuquerque –

Around 3:30 PM, a plane crash was reported near Double Eagle Airport. Officers from the Albuquerque Police Department and crews from Albuquerque Fire Rescue and Bernalillo County Fire Rescue responded to the scene.

Upon arrival, first responders located one injured individual. The female patient sustained an extremity fracture and multiple lacerations and was reported to be in serious condition. She was transported to a local hospital for medical treatment.

We reached out to the Albuquerque Police Department and Albuquerque International Sunport for comment. APD confirmed that a small plane had crashed.

The New Mexico State Police will respond to lead the investigation, which will be conducted in coordination with the National Transportation Safety Board.

This is a developing story. Updates will be provided as more information becomes available.

Update:

Albuquerque Fire Rescue released an update that stated:

“On May 31st at approximately 3:30pm, Albuquerque Fire Rescue was dispatched to Double Eagle Airport for a report of a small airplane crash. The first arriving unit was Bernalillo County Fire Engine 66. CE66 took command and gave a triage report of one patient who was already extricated from the aircraft with moderate injuries. No smoke of flames were present at the crash scene at time of arrival. County Engine 66 (CE66), County Rescue 66 (CR66), AFR Engine 22 (E22), and AFR Rescue 22 (R22) stabilized the scene within minutes of arrival, provided patient care and transport via Albuquerque Ambulance to a local hospital. AFR crews worked collaboratively with Bernalillo County Fire, Double Eagle Airport personnel, APD, and State Police to address the scene. No injuries to first responders. Law enforcement personnel from APD and State Police secured the scene.”

Plane Crash Injures 1 at Double Eagle Airport

Pilot makes emergency landing in field near Highway 365

by Scott Lawrence

JEFFERSON COUNTY — A pilot did what first responders call a masterful job in making an emergency landing in a field when his small plane had a mechanical failure and he was unable to get to the Jefferson County Regional Airport.

The Jefferson County Sheriff’s Office responded to the aircraft emergency landing late this afternoon in the 2200 block of Highway 365 near Medical Center Boulevard in Port Arthur.

The pilot and co-pilot were able to walk away without any injuries.

Chief Deputy Donta Miller say preliminary information indicates the aircraft experienced a mechanical failure while in flight.

The pilot and co-pilot attempted to reach the runway at the Jack Brooks Regional Airport but were unable to do so. They landed safely in a field on airport property.

https://kfdm.com/news/local/breaking-pilot-makes-hard-landing-in-field-near-highway-365

Small plane crashes in Muskingum County

Kevin Accettulla

DRESDEN, Ohio (WCMH) — A small plane crashed Friday afternoon in Muskingum County.

Ohio State Highway Patrol dispatchers said the plane crashed at about 12:07 p.m. near Spease Road just north of Dresden.

Two people were on board the Boeing-Stearman E75 plane, according to the Federal Aviation Administration. Dispatchers said both people were taken to a hospital. Their conditions were not immediately available.

The FAA is investigating the crash.

https://www.aol.com/articles/small-plane-crashes-muskingum-county-174149000.html?guccounter=1&guce_referrer=aHR0cHM6Ly9hdmlhdGlvbi1zYWZldHkubmV0Lw&guce_referrer_sig=AQAAAAVUCfF_dCnLirntzfReVgy2Yg43cfrRWyV8DUe6mjpvVvxta1NxTBpxPyf5pSqXT5mxAGhJ_4djIr033c7jsdyNresEut_508ZQun8oHrAzNahsVvZeQCawRXQVHtcsLkSCcWxlcrQP-plI5IENHGx5U_9qes2LX5Y0JdGJAchl

Transatlantic jet diverts to Shannon with engine problem

The Clare Herald

A flight from the UK to the Caribbean that suffered a problem with one of its two engines over the North Atlantic, was forced to turn around and divert to Shannon Airport this evening.

Virgin Atlantic flight VS-165 departed Heathrow Airport in England at around 4.30pm bound for Montego Bay in Jamaica. There were 241 passengers and a crew of 12 on board.

The Airbus A330-941 jet was over three hours into its journey when the flight crew advised air traffic controllers in Ireland of their issue. The crew declared an emergency confirming they were operating on one engine after an issue arose with the jet’s number 2 engine.

The crew requested clearance to divert to Shannon Airport and descended from their cruising altitude of 34,000 feet to 20,000 feet after turning back towards Ireland.

Air traffic controllers informed airport authorities of the emergency while the National Ambulance Service (NAS), local authority fire service and Gardaí were also alerted.

A number of NAS resources as well as units of Clare County Fire and Rescue Service from Shannon and Ennis stations were dispatched to the airport in support of the airport’s own fire and rescue service.

The Irish Coast Guard was also alerted the Aran Islands RNLI lifeboat was placed on standby as a precaution.

About 15 minutes before the flight was due to land, airport and local authority fire crews took up positions at designated standby points adjacent to Shannon’s runway.

The flight landed safely at 9.24pm on its one operating engine and was pursued along the runway by fire crews. The jet stopped on the runway to allow fire crews check the aircraft’s undercarriage to ensure the braking system hadn’t overheated during the emergency landing.

Soon afterwards, the crew confirmed they would be able to taxi to the terminal building on their one operating engine. The aircraft was accompanied to its parking position by emergency crews who remained with the plane until all services were stood down at around 10.00pm.

A replacement aircraft was dispatched from Heathrow late on Saturday night to take the passengers back to London.

A Virgin Atlantic spokesperson commented: “Flight VS165 from London Heathrow to Montego Bay on 30 May 2026 was diverted to Shannon, Ireland, as a precautionary measure following a technical issue with the aircraft.”

“The safety and wellbeing of our customers and crew is always our top priority and a replacement aircraft was sent immediately to Shannon to bring customers back to Heathrow where they were all offered accommodation.

We sincerely apologise for the disruption to our customers’ journey, and our teams are in contact with them to discuss their options which include rebooking or a refund.”

A replacement aircraft was immediately sent to Shannon to return customers to London Heathrow where they were offered accommodation. Affected customers are being rebooked on to Montego Bay services subject to availability. Alternatively, they can choose a different destination or request a refund,” the airline added.

https://clareherald.com/news/emergency-response/transatlantic-jet-diverts-to-shannon-with-engine-problem/

Two men survive plane crash near Sheridan 

By Luke Matheson

Two men escaped with only minor injuries after a small plane crashed in Grant County on Sunday afternoon.

The crash occurred near Hurricane Creek along U.S. 270, approximately four miles east of Sheridan.

According to sources at the scene, the aircraft experienced a loss of power while in flight. The pilot attempted an emergency landing on U.S. 270 but struck a road sign, causing the plane to leave the roadway and come to rest in a grassy area on the right side of the westbound lane.

The pilot and a passenger suffered minor abrasions but were able to walk away from the wreckage.

Emergency responders arrived at the scene and assessed both occupants. No serious injuries were reported.

Officials have not yet released the identities of the pilot or passenger.

Arkansas State Police are expected to release additional information about the incident. The Federal Aviation Administration is also expected to investigate the cause of the crash.

Two men survive plane crash near Sheridan 

Plane makes emergency landing at Vitória Airport after landing gear malfunction.

A private aircraft had to make a belly landing on Sunday afternoon (31). According to the terminal's concessionaire, no one was injured and airport operations continued normally.

NC News Editorial Staff

A private plane had to make an emergency landing at Vitória Airport, in Espírito Santo, on Sunday afternoon (31), after experiencing problems with the landing gear system during the flight. The aircraft, a Beech B200 Super King Air model, managed to land safely, and all occupants escaped without injury.

According to Zurich Airport Brasil, the concessionaire responsible for managing the airport, the plane had taken off from Barreiras, in Bahia, when the pilot identified a malfunction related to the landing gear and decided to request authorization to land in Vitória.

The landing took place at approximately 1:05 PM. According to information gathered by local media outlets, the pilot received an alert indicating a possible irregularity in the aircraft's lift system and chose to alter the route as a preventive measure.

During landing, the landing gear was unable to support the weight of the aircraft. As a result, the aircraft gradually touched down on its underside, a maneuver known in aviation as a "belly landing." Despite the visual impact of the scene, the procedure was completed without casualties.

The airline did not disclose how many people were on board at the time of the incident, but confirmed that passengers and crew disembarked safely shortly after landing.

Airport emergency teams were mobilized to monitor the operation and provide support after landing. The terminal reported that it remained open and operating normally, with no need to suspend activities.

The incident occurred less than 24 hours after another emergency landing was recorded at the same airport. On Saturday (30), an Azul aircraft that was flying the route between Porto Alegre and Recife also had to land in Vitória after a technical problem. On that occasion, no one was injured.

Avião faz pouso de emergência no Aeroporto de Vitória após falha no trem de pouso

NTSB Prelim: North American AT-6D

Lead Pilot Reported That The Accident Airplane Appeared To Be Recovering From The Descent Just Before It Impacted Terrain

Location: Bronson, FL Accident Number: ERA26FA166
Date & Time: April 13, 2026, 15:36 Local Registration: N29678
Aircraft: North American AT-6D Injuries: 2 Fatal
Flight Conducted Under: Part 91: General aviation - Personal

On April 13, 2026, about 1536 eastern daylight time, a North American AT-6D, N29678, was destroyed when it was involved in an accident near Bronson, Florida. The two pilots were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

The accident pilot was undergoing a formation flight “check-out” at the time of the accident. The accident airplane was the second airplane in a two-airplane formation flight. The flight departed Williston Regional Airport (X60), Williston, Florida, about 1510 and proceeded northwest at an altitude of about 3,000 ft msl.

The pilot of the lead airplane reported that both airplanes completed a formation sequence and then began their return flight to X60, with the accident airplane in “extended trail formation,” about 1/2-mile behind the lead airplane.

As the formation descended through about 2,700 ft msl, on a southerly heading, the lead airplane performed two 180° direction changes, then completed two circles that terminated in a 30° climb and a 30° bank attitude. The lead pilot observed the accident airplane in a nose high attitude as it banked right. The lead pilot then diverted his attention momentarily to clear his turn, then subsequently observed the accident airplane in a steep, 80° nose-down decent.

As the accident airplane continued to descend below approximately 1,000 ft msl, it rolled right about 3-1/2 times. The lead pilot reported that the accident airplane appeared to be recovering from the decent just before it impacted terrain, which was followed by a postimpact fire.

Examination of the accident site revealed that the wreckage was highly fragmented. All major components of the airplane were accounted for at the accident site. The airplane’s engine, wings, and horizontal stabilizers were impact separated and located in the debris field. Flight control continuity was confirmed to all flight control surfaces through control cables that were fractured consistent with overload separations.

The wreckage was retained for further examination.

FMI: www.ntsb.gov

Today in History

17 Years ago today: On 1 June 2009 Air France flight 447, an Airbus A330-200 was destroyed when it crashed into the sea while on transatlantic flight from Rio de Janeiro-Galeao International Airport, RJ (GIG) to Paris-Charles de Gaulle Airport (CDG). All occupants, 12 crew members an 216 passengers, were killed.

Date: Monday 1 June 2009
Time: 00:14
Type: Airbus A330-203
Owner/operator: Air France
Registration: F-GZCP
MSN: 660
Year of manufacture: 2005
Total airframe hrs: 18870 hours
Cycles: 2644 flights
Engine model: GE CF6-80E1A3
Fatalities: Fatalities: 228 / Occupants: 228
Other fatalities: 0
Aircraft damage: Destroyed, written off
Category: Accident
Location: c 160km NNW off São Pedro and São Paulo Archipelago -    Atlantic Ocean
Phase: En route
Nature: Passenger - Scheduled
Departure airport: Rio de Janeiro/Galeão-Antonio Carlos Jobim International Airport, RJ (GIG/SBGL)
Destination airport: Paris-Charles de Gaulle Airport (CDG/LFPG)
Investigating agency:  BEA
Confidence Rating:  Accident investigation report completed and information captured

Narrative:
Air France flight 447, an Airbus A330-200 was destroyed when it crashed into the sea while on transatlantic flight from Rio de Janeiro-Galeao International Airport, RJ (GIG) to Paris-Charles de Gaulle Airport (CDG). All occupants, 12 crew members an 216 passengers, were killed.

Flight AF447 departed at 19:29 hours local time (May 31) from Rio de Janeiro. The takeoff weight was 232.8t (for a MTOW of 233 t), including 70.4 tonnes of fuel. One of the co-pilots was Pilot Flying (PF).
The flight progressed as planned with the crew contacting several air traffic control centres along the way. Cruising altitude was FL350.
At 23:35 local time (01:35 UTC), the crew informed the Atlantic Area Control Centre (CINDACTA III) controller that they had passed the INTOL waypoint. INTOL is an RNAV waypoint located in the Atlantic Ocean, 565 km from Natal, Brazil.
At 01:48 UTC the aircraft went out of the radar coverage of CINDACTA III, Fernando de Noronha. The meteorological situation in the area of AF447's flight path over the Atlantic was typical of that encountered in the month of June in the inter-tropical convergence zone. There were powerful cumulonimbus clusters on the route of AF447. Some of them could have been the centre of some notable turbulence.
At 01:55, the captain woke the second co-pilot and said "[...] heÂ’s going to take my place". The captain then attended the briefing between the two co-pilots, during which the Pilot Flying said, in particular "the little bit of turbulence that you just saw [...] we should find the same ahead [...] weÂ’re in the cloud layer unfortunately we canÂ’t climb much for the moment because the temperature is falling more slowly than forecast" and that "the logon with Dakar failed". The captain left the cockpit at 02:01:46 UTC.

The airplane was flying at FL350 and at Mach 0.82 and the pitch attitude was about 2.5 degrees. Autopilot 2 and auto-thrust were engaged. At 02:06:04, the PF called the cabin crew, telling them that "in two minutes we should enter an area where itÂ’ll move about a bit more than at the moment, you should watch out" and he added "IÂ’ll call you back as soon as weÂ’re out of it".
At 02:08:07, the PNF said "you can maybe go a little to the left [...]". The airplane began a slight turn to the left, the change in relation to the initial route being about 12 degrees. The level of turbulence increased slightly and the crew decided to reduce the speed to about Mach 0.8.
From 02:10:05, the autopilot then auto-thrust disengaged and the PF said "I have the controls". The airplane began to roll to the right and the PF made a left nose-up input. The stall warning sounded twice in a row. The recorded parameters show a sharp fall from about 275 kt to 60 kt in the speed displayed on the left primary flight display (PFD), then a few moments later in the speed displayed on the integrated standby instrument system (ISIS).
At 02:10:16, the PNF said "so, weÂ’ve lost the speeds" then "alternate law [...]".
The airplaneÂ’s pitch attitude increased progressively beyond 10 degrees and the plane started to climb. The PF made nose-down control inputs and alternately left and right roll inputs. The vertical speed, which had reached 7,000 ft/min, dropped to 700 ft/min and the roll varied between 12 degrees right and 10 degrees left. The speed displayed on the left side increased sharply to 215 kt (Mach 0.68). The airplane was then at an altitude of about 37,500 ft and the recorded angle of attack was around 4 degrees. From 02:10:50, the PNF tried several times to call the captain back.
At 02:10:51, the stall warning was triggered again. The thrust levers were positioned in the TO/GA detent and the PF maintained nose-up inputs. The recorded angle of attack, of around 6 degrees at the triggering of the stall warning, continued to increase. The trimmable horizontal stabilizer (THS) passed from 3 to 13 degrees nose-up in about 1 minute and remained in the latter position until the end of the flight.
Around fifteen seconds later, the speed displayed on the ISIS increased sharply towards 185 kt; it was then consistent with the other recorded speed. The PF continued to make nose-up inputs. The airplaneÂ’s altitude reached its maximum of about 38,000 ft, its pitch attitude and angle of attack being 16 degrees.
At around 02:11:40, the captain re-entered the cockpit. During the following seconds, all of the recorded speeds became invalid and the stall warning stopped. The altitude was then about 35,000 ft, the angle of attack exceeded 40 degrees and the vertical speed was about -10,000 ft/min. The airplaneÂ’s pitch attitude did not exceed 15 degrees and the engines' N1's were close to 100%. The airplane was subject to roll oscillations that sometimes reached 40 degrees. The PF made an input on the sidestick to the left and nose-up stops, which lasted about 30 seconds.
At 02:12:02, the PF said "I donÂ’t have any more indications", and the PNF said "we have no valid indications". At that moment, the thrust levers were in the IDLE detent and the engines' N1's were at 55%. Around fifteen seconds later, the PF made pitch-down inputs. In the following moments, the angle of attack decreased, the speeds became valid again and the stall warning sounded again.
At 02:13:32, the PF said "weÂ’re going to arrive at level one hundred". About fifteen seconds later, simultaneous inputs by both pilots on the sidesticks were recorded and the PF said "go ahead you have the controls".
The angle of attack, when it was valid, always remained above 35 degrees. The recordings stopped at 02:14:28. The last recorded values were a vertical speed of -10,912 ft/min, a ground speed of 107 kt, pitch attitude of 16.2 degrees nose-up, roll angle of 5.3 degrees left and a magnetic heading of 270 degrees. The airplane struck the surface of the sea.

Several attempts were made to locate the wreckage of the airplane. Finally on April 2, 2011, a search vessel using unmanned submarines located pieces of wreckage including an engine, landing gear and fuselage and wing parts on the Ocean floor. The flight recorders were recovered on May 2, 2011.

CAUSES OF THE ACCIDENT:
The obstruction of the Pitot probes by ice crystals during cruise was a phenomenon that was known but misunderstood by the aviation community at the time of the accident. From an operational perspective, the total loss of airspeed information that resulted from this was a failure that was classified in the safety model. After initial reactions that depend upon basic airmanship, it was expected that it would be rapidly diagnosed by pilots and managed where necessary by precautionary measures on the pitch attitude and the thrust, as indicated in the associated procedure.
The occurrence of the failure in the context of flight in cruise completely surprised the pilots of flight AF 447. The apparent difficulties with aeroplane handling at high altitude in turbulence led to excessive handling inputs in roll and a sharp nose-up input by the PF. The destabilisation that resulted from the climbing flight path and the evolution in the pitch attitude and vertical speed was added to the erroneous airspeed indications and ECAM messages, which did not help with the diagnosis.
The crew, progressively becoming de-structured, likely never understood that it was faced with a 'simple' loss of three sources of airspeed information.
In the minute that followed the autopilot disconnection, the failure of the attempts to understand the situation and the de-structuring of crew cooperation fed on each other until the total loss of cognitive control of the situation. The underlying behavioural hypotheses in classifying the loss of airspeed information as 'major' were not validated in the context of this accident. Confirmation of this classification thus supposes additional work on operational feedback that would enable improvements, where required, in crew training, the ergonomics of information supplied to them and the design of procedures.
The aeroplane went into a sustained stall, signalled by the stall warning and strong buffet. Despite these persistent symptoms, the crew never understood that they were stalling and consequently never applied a recovery manoeuvre. The combination of the ergonomics of the warning design, the conditions in which airline pilots are trained and exposed to stalls during their professional training and the process of recurrent training does not generate the expected behaviour in any acceptable reliable way.
In its current form, recognizing the stall warning, even associated with buffet, supposes that the crew accords a minimum level of 'legitimacy' to it. This then supposes sufficient previous experience of stalls, a minimum of cognitive availability and understanding of the situation, knowledge of the aeroplane (and its protection modes) and its flight physics. An examination of the current training for airline pilots does not, in general, provide convincing indications of the building and maintenance of the associated skills.
More generally, the double failure of the planned procedural responses shows the limits of the current safety model. When crew action is expected, it is always supposed that they will be capable of initial control of the flight path and of a rapid diagnosis that will allow them to identify the correct entry in the dictionary of procedures. A crew can be faced with an unexpected situation leading to a momentary but profound loss of comprehension. If, in this case, the supposed capacity for initial mastery and then diagnosis is lost, the safety model is then in 'common failure mode'. During this event, the initial inability to master the flight path also made it impossible to understand the situation and to access the planned solution.
Thus, the accident resulted from the following succession of events:
- Temporary inconsistency between the airspeed measurements, likely following the obstruction of the Pitot probes by ice crystals that, in particular, caused the autopilot disconnection and the reconfiguration to alternate law;
- Inappropriate control inputs that destabilized the flight path;

Scroll To Top