Skip to content

Monday the 2nd of June, 2025

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

Be safe out there!

Tom

Small plane goes off runway at Centennial Airport

by: Abraham Jewett

DENVER (KDVR) — South Metro Fire Rescue responded to an aircraft emergency at Centennial Airport just before 1 p.m. on Sunday after a small aircraft taxied off the taxilane into the grass, the airport said.

Centennial Airport, in a post on X, said the sole occupant of the plane, a small RV-6 aircraft, exited the plane with no injuries.

SMFR, in a post on X, said the plane was upright on its wheels and that its units were assessing the aircraft for a possible fuel leak/spill.

https://kdvr.com/news/local/small-plane-goes-off-runway-at-centennial-airport/

Small plane crash near Tulsa International leaves 2 with minor injuries

Authorities say two people walked away from a crash involving a small plane in Tulsa on Friday, May 30, 2025.

By: Drake Johnson

TULSA, Okla. -

A small plane with two people on board crash landed near the Tulsa International Airport on Friday, authorities say.

Emergency crews responded to the scene just after 4:30 p.m. near 6900 E. Virgin Street.

The Tulsa Fire Department confirmed to News On 6 that the two on board, who have not yet been identified, both walked away from the crash with minor injuries. They were taken to a local hospital.

They said some power lines were taken down my the plane during the landing and that PSO (Public Service Oklahoma) was there to assess the damage and make repairs. Tulsa Police said he plane lost power while trying to land and then clipped power lines before landing in the field nearby.

"Please expect traffic delays on the west side of Tulsa International Airport," Police shared on social media.

Flight records show the plane took off from Fort Worth Spinks Airport at 2:53 p.m. and crashed about 4:27 p.m.

Tulsa International Airport said the crash happened south of Tunway 36L, which is the airport's general aviation runway. See the airport's full statement below.

STATEMENT FROM TULSA INTERNATIONAL:

"At approximately 4:26 p.m., a small aircraft struck power lines and crashed south of Runway 36L (Tulsa International Airport’s general aviation runway) while on approach. The aircraft came down outside the secured airfield area. There were no fatalities, and commercial flight operations at Tulsa International Airport have not been impacted. Flights are operating on schedule without delays. Emergency responders from Tulsa Fire Department, Airport Police, EMSA, and Tulsa Police Department arrived on scene immediately. Two individuals were on board the aircraft and were transported by EMSA to a nearby hospital for treatment. Aircraft Information: • Type: Fixed-wing, single-engine Piper PA-32RT-300T • Departure Airport: Fort Worth Spinks Airport (FWS) • Departure Time: 2:52 p.m. • Crash Location: South of Runway 36L at Tulsa International Airport (TUL) • Time of Incident: 4:26 p.m."

https://www.news9.com/story/683a286ac9084378aa163c91/small-plane-crash-lands-near-tulsa-international-airport

Small plane skids off runway and into Lake Washington

KIRO 7 News Staff

The Renton Police Department says a small plane skidded off the runway and into Lake Washington Sunday afternoon.

It happened at the north end of the Renton Airport.

The pilot and passenger weren’t hurt and were able to climb out of the plane.

The National Transportation Safety Board (NTSB) and the Federal Aviation Administration (FAA) have been notified of the crash and will investigate the cause.

https://www.yahoo.com/news/small-plane-skids-off-runway-224603528.html?guccounter=1&guce_referrer=aHR0cHM6Ly9hc24uZmxpZ2h0c2FmZXR5Lm9yZy93aWtpYmFzZS81MTYxMjI&guce_referrer_sig=AQAAANq66ioQY-PLJTgHBlozOypEYHr-G6PY0zc3AwPAYphTxFpYzTnTr-FdOne0JYNmBHT29MGVs-BUK2Rlht-dSIVLQ_LjbMIXP13bzET9G2KslfVrX3jiGr0wJrFatxY2sWbYL_KJjDB_h-WIs-ZTYoYzczhOro5sdg84fVFdSdPp

Pilot injured in small plane crash near Kooskia, Idaho

by DFortin

According to Kooskia Emergency Services, the crash occurred around 9:30 a.m. on Saturday near milepost 24.5 on Highway 13, just south of Kooskia.

Kooskia Ambulance and the Kooskia Fire Department were dispatched to the scene. The pilot, who was the only person on board, had already been extricated before crews arrived.

The pilot was transported by Kooskia Ambulance for further medical evaluation.

https://www.fox28spokane.com/pilot-injured-in-small-plane-crash-near-kooskia-idaho/

The cabin was filled with smoke and the flight returned. China Southern Airlines announced the details

Jimu News reporter Wang Can

On May 31, the passenger posted on a social media platform that a plane from Hangzhou to Shenzhen had a fire in the rear cabin and had to return. Jimu News reporters checked the official website of Hangzhou Xiaoshan International Airport and found that at 10:38 that day, a China Southern Airlines flight from Hangzhou to Shenzhen did return, with flight number CZ6850. A China Southern Airlines customer service staff member responded to the reporter that CZ6850 returned after taking off that day due to passenger reasons, and the specific reason was unknown.

According to the video posted by netizens, there was thick smoke in the cabin at the time and some passengers stood up to assist the flight attendants in handling the situation.

The above-mentioned customer service employee of China Southern Airlines said that the scheduled take-off time of CZ6850 after returning was changed to 12:30, and the specific time is subject to the actual take-off. According to the Air Travel APP, the aircraft operating CZ6850 was an Airbus A320.

According to the Air Travel APP, CZ6850 took off from Hangzhou Xiaoshan International Airport at 10:15 on May 31, and returned at 10:38, landing at Hangzhou Xiaoshan International Airport. Air Travel APP shows that the flight's next scheduled take-off time is yet to be determined.

On the same day, a staff member of Zhejiang Airport Public Security Bureau told reporters that the police were investigating the relevant situation.

On May 31, China Southern Airlines issued a notice on its official website: On flight CZ6850 from Hangzhou to Shenzhen, a passenger's camera battery and power bank began to smoke. The crew handled it properly and quickly eliminated the safety risk. To ensure safety, the crew immediately returned to the airport, and the flight landed safely 15 minutes after takeoff. The company actively provides follow-up service support for passengers. The company reminds passengers to strictly abide by civil aviation safety regulations, properly carry and use similar equipment, and ensure safe travel.

https://news.ifeng.com/c/8jnwHE2NJpc

NTSB Prelim: Champion 7ECA

Patient Told The First Responders That The “Man Who Was In The Plane Was Flying At The Time Of The Accident And Had Overshot The Runway They Were Attempting To Land On.”

Location: Cottonwood, CA Accident Number: WPR25FA145
Date & Time: April 29, 2025, 15:34 Local Registration: N6310N
Aircraft: Champion 7ECA Injuries: 2 Fatal
Flight Conducted Under: Part 91: General aviation - Instructional

On April 29, 2025, at 1534 Pacific daylight time, a Champion 7ECA, N6310N, was destroyed when it was involved in an accident near Cottonwood, California. The flight instructor and pilot receiving instruction were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 instructional flight.

A witness, who was friend of both pilots, and located at the Red Bluff Municipal Airport (RBL), Red Bluff, California, reported that about 30 minutes prior to the accident, he observed the pilots at the airport and approached them for general conversation. He observed the flight instructor seated in the front and the rear seated pilot was undergoing instruction for his flight instructor certificate. According to the witness, the flight instructor was acting as a student pilot, and rear-seated pilot was acting as the flight instructor in preparation for an upcoming a check ride.

First responders located near the accident site reported that they observed black smoke rising toward the sky. When they arrived at the accident site location, they saw the airplane adjacent to a residence as well as a person (later identified as an occupant of the airplane), walking around the area. They began to extinguish the fire and render aide to the patient. The first responders stated that the patient was alert and able to tell them that he self-extricated from the airplane and someone else, the flight instructor, was still in the airplane. The patient told the first responders that the “man who was in the plane was flying at the time of the accident and had overshot the runway they were attempting to land on.” He added that the pilot flying “powered up and then lost control of the [air]plane.”

Examination of the accident site revealed that the airplane impacted several trees and came to rest at a base of a tree about 585 ft south of the departure end of runway 16 at the Flying N Ranch Airport (CA04), Cottonwood, California. The first identified point of contact (FIPC) was a downed fence post located about 40 ft south of the departure end of the runway, aligned on an extended centerline. The downed fence post was about 5 ft in height and was separated at the base. The downed fence post exhibited a black transfer mark near the top of the post. A tree, about 40 ft tall, was about 380 ft south of the FIPC, had damaged limbs near the top of the tree. The debris path was oriented along a heading of about 355° magnetic and about 100 ft in length from the FIPC to the main wreckage. The fuselage came to rest on its left side in an approximate 10° nose low attitude, on a heading of about 310° magnetic, at an elevation of 538 ft mean sea level (msl). The right wing and left main landing gear were separated from the fuselage and located about 5 to 10 north of the main wreckage.

The wreckage was recovered to a secure location for further examination

FMI: www.ntsb.gov

 

 

NTSB Final Report: Bellanca 8GCBC

(Pilot) Inadvertently Applied Excessive Braking Action, And The Airplane Nosed Over

Location: Lime Village, Alaska Accident Number: ANC24LA087
Date & Time: August 31, 2024, 12:40 Local Registration: N1217E
Aircraft: Bellanca 8GCBC Aircraft Damage: Substantial
Defining Event: Nose over/nose down Injuries: 1 None
Flight Conducted Under: Part 91: General aviation - Personal

Analysis: The pilot reported that, while landing at a remote, rough and uneven airstrip in a tailwheel-equipped airplane, he encountered several strong gusts of wind from the left, which pushed the airplane to the right. He said the right main wheel subsequently contacted an area of soft tundra-covered terrain, which resulted in a rapid deceleration. During the rapid deceleration, he inadvertently applied excessive braking action, and the airplane nosed over, sustaining substantial damage to the left wing, lift struts and empennage.

The pilot reported no pre-impact 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 excessive braking during the landing roll, resulting in a nose over.

FMI: www.ntsb.gov

 

 

NTSB Prelim: Rutan Long-Eze

Left Brake Failed, And The Airplane Veered Right And Exited The Runway

Location: Tucson, AZ Accident Number: WPR25LA148
Date & Time: May 1, 2025, 10:30 Local Registration: N433EZ
Aircraft: Rutan Long-Eze Injuries: 1 None
Flight Conducted Under: Part 91: General aviation - Personal

On May 1, 2025, about 1030 mountain standard time, an experimental amateur-built Long EZE, N433EZ, was substantially damaged when it was involved in an accident near Tucson, Arizona. The pilot was not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.

The pilot departed Ryan Field Airport (RYN), Tucson, Arizona, and flew to Marana Regional Airport (AVQ), Marana, Arizona, and accomplished a low approach to the runway. The pilot then returned to RYN for a full stop landing on runway 6R. He reported that during the landing roll, the left brake failed, and the airplane veered right and exited the runway. Subsequently, the airplane’s left canard struck a runway sign, which resulted in substantial damage to the canard. The airplane came to rest about 20 ft off the right side of runway.

The airplane was secured for further examination.

FMI: www.ntsb.gov

Today in History

42 Years ago today: On 2 June 1983 Air Canada flight 797, a DC-9-30, diverted to Cincinnati Airport, Kentucky, USA, after an in-flight fire had developed en route, killing 23 occupants; 23 survived the accident.

Date: Thursday 2 June 1983
Time: 19:20
Type: McDonnell Douglas DC-9-32
Owner/operator: Air Canada
Registration: C-FTLU
MSN: 47196/288
Year of manufacture: 1968
Total airframe hrs: 36825 hours
Cycles: 34987 flights
Engine model: P&W JT8D-7B
Fatalities: Fatalities: 23 / Occupants: 46
Other fatalities: 0
Aircraft damage: Substantial, written off
Category: Accident
Location: Cincinnati/Northern Kentucky Airport, KY (CVG) -    United States of America
Phase: En route
Nature: Passenger - Scheduled
Departure airport: Dallas/Fort Worth International Airport, TX (DFW/KDFW)
Destination airport: Toronto International Airport, ON (YYZ/CYYZ)
Investigating agency:  NTSB
Confidence Rating:  Accident investigation report completed and information captured

Narrative:
Air Canada flight 797, a DC-9-30, diverted to Cincinnati Airport, Kentucky, USA, after an in-flight fire had developed en route, killing 23 occupants; 23 survived the accident.

Flight AC797, a McDonnell Douglas DC-9-32, was a scheduled flight from Dallas (DFW) to Montreal, Canada, with an en route stop at Toronto (YYZ).
At 16:25 CDT, Flight 797 left Dallas and climbed to FL330. Except for a deviation to the south of their filed flight plan route to avoid weather, the flight progressed without incident until it entered the Indianapolis Air Route Traffic Control Center's (ARTCC) airspace.
At 18:51:14 EDT, the three circuit breakers associated with the aft lavatory's flush motor and located on a panel on the cockpit wall behind the captain's seat, tripped in rapid succession. After identifying the circuit breakers, the captain immediately made one attempt to reset them; the circuit breakers would not reset. The captain assumed that the flush motor had probably seized and took no further action at this time. About 18:59:58, the captain again unsuccessfully tried to reset the three circuit breakers. He told the first officer that the circuit breaker "Pops as I push it." About 19:00, a passenger seated in the last row asked a flight attendant to identify a strange odor. The flight attendant thought the odor was coming from the aft lavatory. She took a CO2 fire extinguisher from the cabin wall and opened the lavatory door a few inches. She saw that a light gray smoke had filled the lavatory from the floor to the ceiling, but she saw no flames. While she was inspecting the lavatory, she inhaled some smoke and closed the door. The No.3 flight attendant then saw the No.2 flight attendant nearby and asked her to tell the flight attendant in charge of the situation. Upon being advised there was a fire, the flight attendant in charge instructed the No. 2 flight attendant to inform the captain and then to assist the No. 3 flight attendant in moving the passengers forward and in opening the eyebrow air vents over the passenger seats to direct air to the rear of the cabin. The flight attendant in charge then took the CO extinguisher and opened the lavatory door about three-quarters open. He also saw no flames, but he observed thick curls of black smoke coming out of the seams of the aft lavatory walls at the top of the wash basin behind the vanity and at the ceiling. He then proceeded "to saturate the washroom with CO'' by spraying the paneling and the seam from which smoke was seeping and spraying the door of the trash bin. He then closed the lavatory door.
At 19:02:40, the No. 2 flight attendant reached the cockpit and told the captain, "Excuse me, there's a fire in the washroom in the back, they're just ... went back to go to put it out." Upon being notified of the fire, the captain ordered the first officer to inspect the lavatory. The captain then donned his oxygen mask and selected the 100-percent oxygen position on his regulator. The first officer left the cockpit but did not take either smoke goggles or a portable oxygen bottle with him. (The airplane was not equipped with nor was it required to be equipped with self-contained breathing equipment or a full face smoke mask.) The first officer said that he could not get to the aft lavatory because the smoke, which had migrated over the last three to four rows of seats, was too thick. The flight attendant in charge told the first officer what he had seen when he opened the lavatory door, that he had discharged the CO2 extinguisher into the lavatory, and that he had not been able to see the source of the smoke before closing the door. He told the first officer, however, that he did not believe the fire was in the lavatory's trash container. The first officer told the flight attendant in charge that he was going forward to get smoke goggles. At 19:04:07, the first officer returned to the cockpit and told the captain that the smoke had prevented him from entering the aft lavatory and that he thought "we'd better go down." He did not tell the captain that the flight attendant in charge had told him that the fire was not in the trash bin. However, at 19:04:16, before the captain could respond, the flight attendant in charge came to the cockpit and told the captain that the passengers had been moved forward and that the captain didn't "have to worry, I think its gonna be easing up." The first officer looked back into the cabin and said that it was almost clear in the back. He told the captain, "it's starting to clear now," and that he would go aft again if the captain wanted him to do so. According to the captain, the first officer's smoke goggles were stored in a bin on the right side of the cockpit and were not easily accessible to the first officer while he was not in his seat. Since the first officer needed the goggles and since there was a hurry, the captain gave him his goggles and, at 19:04:46, directed him to go aft.
Two minutes later, while the first officer was out of the cockpit, the flight attendant in charge told the captain again that the smoke was clearing. The captain believed the fire was in the lavatory trash bin and decided not to descend at this time because he "expected it (the fire) to be put out." About 19:05:35, while the first officer was still aft to inspect the aft lavatory, the airplane experienced a series of electrical malfunctions. The master caution light illuminated, indicating that the airplane's left a.c. and d.c. electrical systems had lost power.
In the meanwhile, the first officer proceeded to the aft lavatory and put on the smoke goggles. The lavatory door felt hot to the touch, so he decided not to open it and instructed the cabin crew to leave it closed. At that time, he noticed a flight attendant signaling him to hurry back to the cockpit. The first officer returned to the cockpit and got into his seat, and at 19:07:11, he told the captain, "I don't like what's happening, I think we better go down, okay?" Then the master warning light illuminated and the annunciator lights indicated that the emergency a.c. and d.c. electrical buses had lost power. The captain's and first officer's attitude directional indicators tumbled. The captain ordered the first officer to activate the emergency power switch, thereby directing battery power to the emergency a.c. and d.c. buses. The attitude directional indicators' gyros began erecting, however, because of the loss of a.c. power, the stabilizer trim was inoperative and remained so during the rest of the flight. At 19:08:12, Flight 797 called the radar high sector controller at Indianapolis Center: "Mayday, Mayday, Mayday." The Louisville radar high sector controller acknowledged the call, and at 19:08:47, the flight told the controller that it had a fire and was going down. The controller told the flight that it was 25 nautical miles from Cincinnati and asked "can you possibly make Cincinnati." The flight answered that it could make Cincinnati and then requested clearance; it was then cleared to descend to 5,000 feet. At 19:09:05, Flight 797 reported that it was leaving FL330. The flight then told the controller that it needed to be vectored toward Cincinnati, that it was declaring an emergency, and that it had changed its transponder code to 7700 -- the emergency code. However, the transponder was inoperative due to the power loss.
The Louisville radar high sector controller directed the flight to turn to 060 degrees and told it that the Greater Cincinnati Airport was at "twelve o'clock at twenty miles." The Indianapolis Center's Lexington low altitude D (LEX-D) controller then called the approach controller at the Cincinnati Airport's Terminal Radar Control (TRACON) facility to alert him of an impending handoff in his southwest sector and later told the Cincinnati approach controller that he had "an emergency for you, Air Canada seven nine seven." The approach controller replied, "Zero six six two, thirty-five thousand." Zero six six two was the code assigned to Continental 383, a westbound flight at FL350. At 19:09:33, the LEX-D controller answered, "Yeah, thirty-three right now, he's twenty-five southwest." The approach controller replied, "Radar contact, okay." However, when the approach controller accepted the handoff of Flight 797, he had mistaken the radar beacon target of Continental Flight 383 as that of Flight 797. Shortly after he had accepted the handoff, the approach controller had notified the Cincinnati Airport tower local controller that he intended to land an Air Canada jet with an on board fire on runway 36. The tower's local controller alerted the airport fire station, and crash-fire-rescue (CFR) vehicles were dispatched and positioned for an emergency landing. The firefighters had also been advised that the airplane had electrical problems, that smoke was coming from the aft lavatory, and that there was smoke or fire in the rear of the airplane. At 19:10:01, almost coincident with the end of his message to the local controller, the LEX-D controller informed the approach controller of Flight 797's assigned 060° heading. At 19:10:25, Flight 797 contacted the Cincinnati approach controller, declared an emergency, and said that it was descending. The approach controller acknowledged and told the flight to plan for a runway 36 instrument landing system (ILS) approach and requested the flight to turn right to 090 degrees. He then realized the target he was observing was not responding and attempted unsuccessfully to assign a discrete transponder code to it in order to track it better. Thereafter, at 19:10:48, Flight 797 reported that it had a fire in its aft lavatory and that the cabin was filling with smoke. The controller asked the flight to "say the type airplane, number of people on board, and amount of fuel (on board)." The first officer answered that he would supply this data later because "I don't have time now." At 19:12:40, the approach controller called the Evansville/Nabb D controller on the landline to request assistance. Almost simultaneous with the call, he also observed an eastbound primary target and began to monitor it. At 19:12:44, the flight requested the cloud ceiling at the airport and the controller responded that the ceiling was "two thousand five hundred scattered, measure(d) eight thousand feet overcast, visibility one two (12) miles with light rain." The controller then decided that the eastbound target was Flight 797, and at 19:12:54, he requested the flight to "say altitude." Based on the target's position -- about 3 nmi east of runway 36's extended centerline and about 8 nmi south of its threshold -- and its reported altitude of 8,000 feet, that it was too high and too fast to land on runway 36. He decided to use runway 27L for landing, and used the primary target to monitor the flight and vector it toward the airport. At 19:13:38, after Flight 797 was unable to tell him its heading because its heading instruments were inoperative, the approach controller asked the flight to turn left. The controller said that this was an identification turn and that it was also designed to place the airplane closer to the airport. He then told the flight that this was a "no gyro" radar approach for runway two seven left ... If and cleared it to descend to 3,500 feet. He then told the flight that it was 12 nmi southeast of the Cincinnati Airport, cleared it to land on runway 27L, and informed it that the surface wind was 220 degrees at 4 knots. He informed the tower of the change of landing runways and the tower directed the fire department to position its vehicles along runway 27L. At 19:15:11, Flight 797 reported that it was level at 2,500 feet." The approach controller vectored the flight to runway 27L, and at 19:15:58, told it that it was 12 nmi from the airport. The flight descended to 2,000 feet, and the controller continued to supply range calls.
When the captain sighted the runway, he extended the landing gear. Since the horizontal stabilizer was inoperative, the captain extended the flaps and slats incrementally through the 0, 5, 15, 25, and 40-degree positions. He allowed his indicated airspeed to stabilize at each flap position as he slowed to approach speed. He flew the final approach at 140 KIAS and completed the landing. After touchdown, he made a maximum effort stop using extended spoilers and full brakes. Because of the loss of the left and right a.c. buses, the antiskid system was inoperative and the four main wheel tires blew out. The airplane was stopped just short of the intersection of taxiway J. After the captain completed the emergency engine shutdown checklist, both he and the first officer attempted to go back into the cabin and assist in the passenger evacuation, but were driven back by the smoke and heat. Thereafter, they exited the airplane through their respective cockpit sliding windows. After the airplane stopped, the left (L-1) and right (R-1) forward cabin doors, the left forward (L-2) overwing exit, and the right forward (R-2) and aft (R-3) overwing exits were opened, and the slides at the L-1 and R-1 doors were deployed and inflated. The 3 cabin attendants and 18 passengers used these 5 exits to evacuate the airplane. After the 18 passengers and 5 crewmembers left the airplane, the cabin interior burst into flames. Twenty-three passengers perished in the fire. Neither the passengers, crew, nor witnesses outside of the airplane saw flames inside the cabin before the survivors left the plane. The fuselage and passenger cabin were gutted before airport fire personnel could extinguish the fire.

PROBABLE CAUSE: "A fire of undetermined origin, an underestimate of fire severity, and conflicting fire progress information provided to the captain.
Contributing to the severity of the accident was the flight crew's delayed decision to institute an emergency descent."

Scroll To Top