Skip to content

Monday the 8th of December, 2025

We start the new week with these stories...

Be safe out there!

Tom

-

Small plane damaged after crashing on runway in Montgomery County

By 6abc Digital Staff

BLUE BELL, Pa. (WPVI) -- Officials are investigating a small plane crash in Montgomery County.

It happened just before 3 p.m. Sunday on the runway at Wings Field in Blue Bell.

The small plane had minor damage to the nose and front landing gear.

There have been no reports of any injuries.

The cause of the crash is under investigation.

https://6abc.com/amp/post/small-plane-damaged-crashing-runway-blue-bell-pennsylvania/18263688/

AJet Pristina flight skids off runway in Istanbul

EX-YU Aviation News

An AJet Boeing 737-800 operating a scheduled service from Pristina to Istanbul Sabiha Gokcen Airport veered and skidded off the runway upon landing this evening (pictured), coming to a stop on an unpaved area adjacent to the taxiway.

All passengers on flight VF102 were safely evacuated from the aircraft. One of Sabiha Gokcen’s runways has been temporarily closed as a result of the incident.

The aircraft is understood to have landed in rainy conditions, with a wet runway surface at the time.

Emergency services were swiftly deployed to assess potential damage to the aircraft and infrastructure. There are currently no reports of injuries among passengers or crew.

https://www.exyuaviation.com/2025/12/ajet-pristina-flight-skids-off-runway.html?m=1#google_vignette

Small aircraft incident at Pensacola airport causes minor injuries

by Hannah James

PENSACOLA, Fla. -- Several people were injured in a small airplane crash at Pensacola International Airport on Sunday night.

Two runways were closed while first responders cleaned up the site.

The National Transportation Safety Board will investigate the crash.

Officials say the incident occured around 5:30 p.m.

Executive director of the airport, Matt Coughlin, says the 'Cessna 172' took off from runway 08 before crashing into a treeline on airport property.

https://weartv.com/news/local/small-aircraft-incident-in-pensacola-results-in-minor-injuries-ems-on-scene

NTSB Final Report: Piper PA-31T3

As He Released The Brakes To Begin Taxiing, The Brake Pedals Went To The Floor With No Braking Action

Location: Appleton, Wisconsin Accident Number: CEN25LA293
Date & Time: July 26, 2025, 07:45 Local Registration: N401VA
Aircraft: Piper PA-31T3 Aircraft Damage: Substantial
Defining Event: Loss of control on ground Injuries: 1 None
Flight Conducted Under: Part 135: Air taxi & commuter - Non-scheduled

Analysis: The pilot reported that during engine start up, he applied the brakes to the cargo airplane and remained stationary while he received a taxi clearance. As he released the brakes to begin taxiing, the brake pedals went to the floor with no braking action. He pumped the brakes several times with no effect, so he feathered both propellers and shut down the engines. The airplane continued to roll and collided with a parked airplane on the ramp.

Postaccident examination revealed that the airplane sustained substantial damage to the left wing. A functional check revealed that the brake system was operational with no malfunctions noted. The left main landing gear brake pads were worn beyond allowable limits. The examination did not reveal any other anomalies that would have precluded normal operation. While the left brake pads were worn beyond allowable limits, the main landing gear braking action would have still been available to the pilot.

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 control of the airplane on the ground, which resulted in a collision with a parked airplane.

FMI: www.ntsb.gov

 

 

NTSB Final Report: Lafferty Jack Sea Rey

While Landing In The River, The Extended Landing Gear Contacted The Water And The Airplane Nosed Over, Resulting In Substantial Damage

Location: Bell, Florida Accident Number: ERA25LA335
Date & Time: September 6, 2025, 12:52 Local Registration: N2469J
Aircraft: Lafferty Jack Sea Rey Aircraft Damage: Substantial
Defining Event: Landing gear not configured Injuries: 2 None
Flight Conducted Under: Part 91: General aviation - Personal

Analysis: The pilot of the amphibious airplane stated that he departed from a turf runway at his home airport but forgot to raise the landing gear. He planned a short flight to a nearby river where he would make a water landing, before returning to his home airport. While landing in the river, the extended landing gear contacted the water and the airplane nosed over, resulting in substantial damage to the forward portion of the fuselage. The pilot stated that there were no preimpact mechanical malfunctions or failures of 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 failure to raise the landing gear before landing on the water.

FMI: www.ntsb.gov

 

 

NTSB Final Report: Patriot Aircraft LLC CX1900A

After Draining Both Wing Fuel Tanks, A Significant Amount Of Water Was Observed In The Right Wing Fuel Tank

Location: Centreville, Alabama Accident Number: ERA25LA315
Date & Time: August 20, 2025, 09:00 Local Registration: N150SP
Aircraft: Patriot Aircraft LLC CX1900A Aircraft Damage: Substantial
Defining Event: Fuel contamination Injuries: 1 Serious, 1 Minor
Flight Conducted Under: Part 91: General aviation - Business

Analysis: The pilot, who was also the owner of the experimental amateur-built airplane’s kit manufacturer, was performing a demonstration flight for potential buyers. The pilot reported that after fueling the airplane, a preflight inspection was performed and no anomalies were found; however, he stated that he did not sump the fuel tanks or the low-point drains. The pilot stated that after performing the engine runup and allowing the engine to reach operating temperatures, he performed a normal take off. At around 300 ft above ground level, the pilot reported that the engine began to “cut out,” and the pilot pulled the throttle bringing the engine to idle. He then began a left turn back toward the runway and advanced the throttle; however, the engine lost complete power. The pilot realized that he would not make it back to the runway and performed a forced landing into a wooded area.

A postaccident examination of the airplane revealed that it had sustained substantial damage to the wings. Examination of the engine found evidence of water in the fuel flow divider. After draining both wing fuel tanks, a significant amount of water was observed in the right wing fuel tank. According to the pilot, there were no fueling services available at the departure airport, and so he would fill barrels with fuel and store the barrels at the airport. According to the individuals who fueled the airplane that morning, when fueling the right fuel tank, they needed to tip the fuel barrel all the way on its side to get the last remaining fuel. Based on this information, it is likely that when the right fuel tank was filled, water that had accumulated in the fuel barrel was poured into the right fuel tank, which was then not drained during the preflight inspection. Subsequently, during takeoff, water likely entered the engine’s fuel system and cylinders, resulting in the reported loss of power.

Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s failure to detect and remove water contamination from the airplane’s fuel system before the flight, which resulted in a total loss of engine power during initial climb.

FMI: www.ntsb.gov

Today in History

53 Years ago today: On 8 December 1972 United Airlines flight 553, a Boeing 737-200, crashed while on approach to Chicago-Midway Airport, IL, USA, killing 43 occupants and 2 persons on the ground.

Date: Friday 8 December 1972
Time: 14:28
Type: Boeing 737-222
Owner/operator: United Airlines
Registration: N9031U
MSN: 19069/75
Year of manufacture: 1968
Total airframe hrs: 7247 hours
Engine model: P&W JT8D-7B
Fatalities: Fatalities: 43 / Occupants: 61
Other fatalities: 2
Aircraft damage: Destroyed, written off
Category: Accident
Location: 2 km from Chicago-Midway Airport, IL (MDW) -    United States of America
Phase: Approach
Nature: Passenger - Scheduled
Departure airport: Washington-National Airport, DC (DCA/KDCA)
Destination airport: Chicago-Midway Airport, IL (MDW/KMDW)
Investigating agency:  NTSB
Confidence Rating:  Accident investigation report completed and information captured

Narrative:
United Airlines flight 553, a Boeing 737-200, crashed while on approach to Chicago-Midway Airport, IL, USA, killing 43 occupants and 2 persons on the ground.

The aircraft, named "City of Lincoln", took off from Washington-National Airport as United flight 553 to Chicago and Omaha. Departure time was 12:50 CST. Chicago ARTCC cleared the crew to descend to 4000 feet and the flight was given vectors for a Midway Airport runway 31L localizer course. At 14:19 the flight was transferred to Chicago Approach Control which later requested UA553 to slow down to 180 knots and later down to 160 knots. After issuing a descent clearance down to 2000 feet at 14:23 the controller requested the flight to slow down to approach speed because of separation between UA553 and a preceding Aero Commander. At 14:24 the Aero Commander passed the Outer Marker and was cleared to land on runway 31L. Two minutes later UA553 passed the Outer Marker inbound. Then, at 14:27:04 the air traffic controller decided to issue a missed approach clearance: "United 553 execute a missed approach make a left turn to a heading of 180 climb to 2000". At the same time, having just reached 1000 feet, the stick shaker suddenly activated. Full power was applied and the gear was retracted in an attempt to execute a missed approach. The Boeing continued to descend however, attaining a high nose up attitude (of at least 30deg, according to some survivors). The aircraft then clipped a tree and impacted trees, houses, utility pole cables and garages before coming to rest. Post crash fire destroyed part of the fuselage.

PROBABLE CAUSE: "The captain's failure to exercise positive flight management during the execution of a non-precision approach, which culminated in a critical deterioration of airspeed into the stall regime where level flight could no longer be maintained."

Scroll To Top