Here are your stories for today...
Be safe out there!
Tom
--
Pilot, trainee OK after small plane skids off runway while landing at Pompano Beach Airpark
By Rubén Rosario
POMPANO BEACH, FLA. (WSVN) - A pilot and a trainee 
were not hurt when a small plane veered off the runway at Pompano Beach Airpark.
7Skyforce hovered above the Costruzioni P-Mentor next to a rescue vehicle, just off Runway 10 at the airpark, at around 12:35 p.m. on Tuesday.
According to the Federal Aviation Administration, the flight school aircraft was landing when it experienced some issues and skidded off the runway, at around noon.
Both the pilot and the trainee were able to get out safely. They were not hurt.
The FAA is investigating.
2 injured in plane crash at Plymouth Municipal Airport
Ricky Podgorski - Reporter
MANCHESTER, N.H. —
Two passengers were injured Tuesday after a plane crashed at Plymouth Municipal Airport. 
Officials said the crash happened around 4 p.m., forcing a temporary closure of the airport while crews removed the plane and moved it to a hangar.
The passengers were taken to a local hospital and are expected to be OK.
Two Granite Staters who witnessed the aftermath said the plane appeared damaged.
"Saw the ambulance, saw all the cops, saw all the fire trucks, so we slowed down, there was people here and then I could see the plane out there. You could tell that was the one. It was a little crunched. Not terrible, but it was beat up," said Jim Blake of Rumney.
"It looked like it could be fixed," said Wesley Howlett of Rumney.
The Federal Aviation Administration is investigating the cause of the crash.
This is the third small plane crash in New Hampshire in recent weeks. The other two occurred at the same airfield in Jaffrey and are also under investigation by the FAA.
https://www.wmur.com/article/plane-crash-plymouth-new-hampshire-2-hurt-06092026/71539082
Small plane makes emergency landing near Eloy Municipal Airport
By Ben Bradley
ELOY, AZ (AZFamily) — No injuries were reported after a small plane made an emergency landing in a desert area near an airport in Pinal County. 
Tuesday morning, fire crews were called to reports of a possible plane crash north of the Eloy Municipal Airport. First responders arrived to find there was no crash and that the aircraft made an emergency landing in the desert due to engine failure.
The Eloy Fire District reported no one was hurt and that units have since cleared the scene.
The incident is the latest in a series of emergency landings involving small planes in Arizona. Since April, at least six planes have been forced to make emergency landings.
One case involved a plane that landed on a Phoenix roadway after experiencing engine trouble. Weeks later, a plane nearly hit a pickup truck during an emergency landing on U.S. 60 near Superior.
In mid-May, a plane experienced engine failure shortly after takeoff and was forced to land on a state highway near Lake Havasu City.
https://www.kold.com/2026/06/09/small-plane-makes-emergency-landing-near-eloy-municipal-airport/
NTSB Prelim: North American F-51D
According To Witnesses, The Pilot Was Practicing An Aerobatic Routine
Location: Mound, LA Accident Number: CEN26FA184
Date & Time: May 12, 2026, 15:19 Local Registration: N251CS
Aircraft: North American F-51D Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
On May 12, 2026, at 1519 central daylight time, a North American F-51D airplane, N251CS, was destroyed when it was involved in an accident at the Vicksburg Tallulah Regional Airport (TVR), Mound, Louisiana. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to witnesses, the pilot was practicing an aerobatic routine. At the conclusion of the planned maneuvers, the pilot performed an additional maneuver and the airplane impacted terrain. Witnesses reported that the engine sounded normal before they heard the sound of impact. One witness, who was in a nearby hangar, reported seeing flying debris after he heard the sound of impact. A witness captured the accident sequence on a cellular phone video.
According to a witness and the video, the airplane was seen climbing while conducting a maneuver consistent with a Split-S. While inverted, the airplane entered a dive and continued toward the ground in a nose low attitude. The airplane started a bank to the right just before impacting terrain in a nose level, right-wing-low attitude. The engine is heard throughout the entire video up to the sound of impact.
The aerobatic routine was conducted within an FAA approved aerobatic practice area along the west side of runway 18/36 within the boundaries of the aerobatic box defined as a rectangular area 6,200 ft long by 2,600 ft wide, from the surface to 3,000 ft above ground level. The aerobatic practice area was active at the time of the accident.
The airplane impacted a drainage embankment about 450 ft west of runway 18/36. The ground scars at the initial impact site were consistent with a high speed, nose level, and right-wing-low attitude. The debris field extended about 920 ft northeast of the initial impact site and was about 200 ft at its widest point. The debris field extended across a 30 ft wide drainage ditch with about 2 to 3 ft of water. All major components of the airplane were found within the debris field.
The cockpit and majority of the fuselage were about 520 ft from the initial impact site. A propeller blade was embedded in the ground at the initial impact site. The engine separated from the airframe and was found about 690 ft from the initial impact site. The cockpit came to rest on its right side on a 300° heading. The debris field was generally aligned on a 40° heading.
Flight control continuity was confirmed for both ailerons, the elevator, and the rudder. Cable separations were consistent with overload separation due to impact damage. The majority of the fuel system was fragmented and destroyed. Both wing tank fuel bladders were breached and contained no fuel; however, fuel blight was present along the debris path on both sides of the drainage ditch. The four propeller blades exhibited leading edge damage and S-bending consistent with the production of engine power at the time of impact. On site examination of the airframe and engine found no anomalies that would have precluded normal operation.
A Garmin GI275 and GTN650 capable of recording data were collected on-site. The witness video of the accident and recording devices were sent to the NTSB’s Vehicle Recorders laboratory for further investigation.
The airplane was recovered to a secure facility.
FMI: www.ntsb.gov
Today in History
18 Years ago today: On 10 June 2008 Sudan Airways flight 109, an Airbus A310, overran the runway at Khartoum-Civil Airport (KRT) and burst into flames, killing 30 occupants; 184 survived the accident.
| Date: | Tuesday 10 June 2008 |
| Time: | 20:26 |
| Type: | Airbus A310-324 |
| Owner/operator: | Sudan Airways |
| Registration: | ST-ATN |
| MSN: | 548 |
| Year of manufacture: | 1990 |
| Total airframe hrs: | 53233 hours |
| Cycles: | 21524 flights |
| Engine model: | P&W PW4152 |
| Fatalities: | Fatalities: 30 / Occupants: 214 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Khartoum-Civil Airport (KRT) - Sudan |
| Phase: | Landing |
| Nature: | Passenger - Scheduled |
| Departure airport: | Damascus International Airport (DAM/OSDI) |
| Destination airport: | Khartoum-Civil Airport (KRT/HSSS) |
| Investigating agency: | AAICD |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
Sudan Airways flight 109, an Airbus A310, overran the runway at Khartoum-Civil Airport (KRT) and burst into flames, killing 30 occupants; 184 survived the accident.
The aircraft was operated with a deactivated no. 1 engine reverser as per Minimum Equipment List (MEL) procedures, being a carry forward defect. This was accepted by the pilot who operated the return flight from Khartoum to Amman.
Sudan Airways Flight 109 was the return leg from Amman, Jordan to Khartoum, Sudan with an en route stop at Damascus, Syria. The airplane diverted to Port Sudan due to inclement weather at Khartoum. After staying on ground at Port Sudan for about 1:15 hour, and being informed that the weather was getting better, the captain decided to continue to Khartoum.
Weather was poor with CB clouds and a thunderstorm as the Airbus approached Khartoum. The flight was cleared to land on runway 36 with wind information given as 320 degrees at 7 knots. In reality however, there was a 15 knot tail wind. The runway was reported being wet.
The Airbus touched down 900 metres past the runway threshold and the captain selected both thrust reversers to maximum reverse. Reverser no. 2 deployed normally and no. 1 remained stowed. Because of asymmetrical reverse, the airplane skidded to the right. Ten seconds after touch down both reversers were stowed and thrust levers were set to idle. The captain put the aircraft back to the centre line by using differential braking. The captain then switched the anti-skid off and applied full braking on both pedals, causing the wheels to lock. The aircraft longitudinally overran the runway and came to a stop 215 meters after the runway end. Then it caught fire on its right side.
Fire services arrived late at the scene of the accident due to acute shortage in fire fighting personnel, and the fact that there was no means of communication between the fire station and the vehicles.
Cause of the accident:
"The accident was due to a long flaring distance (900 meters from R/W threshold) on a wet slippery runway without selecting Auto brake and with one deactivated engine reverse in such rainy conditions. The remaining available landing distance turned out to be too short to allow the captain to stop the aircraft before the end of the runway.
Contributing factors:
The wind information was not appropriate as it was tail wind at time of landing. The crew was not aware about the aircraft ground speed and the tail wind."
METAR:
14:30 UTC / 17:30 local time:
HSSS 101430Z 12013KT 3000 M TS/RA FEW050CB SCT056 BKN140 Q1011 NO SIG=
17:00 UTC / 20:00 local time:
HSSS 101700Z 27002KT 9/9 TS RA OV ST FEW050 SCT056 BKN140 26/26 Q1013 NO SIG=
18:30 UTC / 21:30 local time:
HSSS 101830Z 15010KT 9/9 FEW050 CB TS TO E SCT 056 Q1010=
19:00 UTC / 22:00 local time:
HSSS 101900Z 14007KT 9/9 FEW050 CB TS TOE SCT056 30/19 Q1010 NO SIG=
