We kick off the new week with these stories...
Be safe out there!
Tom
-
Plane crash in Wesley Chapel neighborhood kills one: PCFR
By WTVT Web Staff and Danielle Zulkosky
The Brief
-
- A plane crashed on Aldus Dr in Wesley Chapel
Sunday morning, according to the Pasco County Fire Rescue. - Officials say one person has died from the plane crash.
- The FAA and NTSB will be leading the investigation.
- A plane crashed on Aldus Dr in Wesley Chapel
WESLEY CHAPEL, Fla. - One person is dead after a plane crashed in a Wesley Chapel neighborhood, according to Pasco County Fire Rescue.
What we know:
PCFR said a twin-engine plane crashed on Aldus Drive Sunday morning.
The plane was a Cessna 401B airplane, according to
the National Transportation Safety Board.
The fire from the crash has since been extinguished, and officials say the Federal Aviation Administration and the National Transportation Safety Board are leading the investigation.
PCFR said at least one home sustained damage from the crash.
One person had died as a result of the crash, officials said.
One neighbor said the plane crashed between three homes, and it was no mistake that the pilot missed the houses.
"I think that the pilot is a hero. He knew that it was going down, and he found a perfect spot to land," said Christina Galbiati, a neighbor who witnessed the crash. "So he went straight in between houses, which I imagine is a pretty hard thing to do."
"He landed right in between those two unfenced yards," Galbiati said. "It takes seconds to make that decision."
What we don't know:
Officials have not shared if anyone else was involved in
the crash.
"We'll pray for them and that kind of thing," said Victoria Barrett, another neighbor who witnessed the crash. "But it's tragic, and we'll see what FAA comes up with the investigation."
Galbiati said the plane sounded loud and weird when it went over her house.
"My kids were in the backyard jumping on their trampoline. They saw a low-flying plane," Galbiati said. "I was in the front yard drinking coffee, and I saw the plane come around and thought it was very, very low, but everything looked mechanically fine. I saw the propellers spinning, no fire or anything."
The backstory:
Neighbors said this is a part of a pattern. FOX 13 reported on a plane crash in the area in 2020.
"This is our fourth crash in this neighborhood after about a few years," Barrett said.
But it will not change their habits or decision to live here.
"It's a nice neighborhood. We like it. We're very happy here," Galbiati said. "I think that things can happen and I don't want to live in fear. So, I do feel safe."
https://www.fox13news.com/news/plane-crashes-wesley-chapel-kills-one-pcfr.amp
Passengers board new plane hours after diversion to Pittsburgh for 'possible security issue'
Caitlyn Scott
PITTSBURGH —
A plane en route to New York was diverted to Pittsburgh International Airport on Saturday due to a "possible security issue," according to officials.
A spokesperson for the Allegheny County Airport
Authority confirmed to Pittsburgh's Action News 4 that United Flight 2092 from O'Hare to LaGuardia was diverted to Pittsburgh just before noon following a possible security concern reported by the airline crew.
Advertisement
The FAA said in a statement that the plane landed safely at PIT around 11:45 a.m. We're told 159 passengers and 6 crew members were on board at the time.
All passengers were evacuated from the plane via slides. No injuries have been reported.
Video from the scene showed the plane stopped on the runway at PIT. It appeared crews were coming to evacuate passengers at the time the video was taken.
A fire truck, along with an ambulance, was seen leaving from the plane following the evacuations.
Police, with aid from the Allegheny County Police Bomb Squad and FBI Pittsburgh Special Agent Bomb Techs and Special Agents, are on the scene investigating.
FBI Pittsburgh issued the following response on the incident, saying:
"FBI Pittsburgh is aware of a reported threat onboard a flight headed to New York. The plane was diverted and landed at Pittsburgh International Airport. All passengers and crew safely evacuated the aircraft. FBI Special Agent Bomb Techs and Special Agents are on the ground coordinating with local authorities. FBI Pittsburgh will provide further updates as appropriate due to the ongoing nature of this investigation."
Following FBI Pittsburgh's statement, the Allegheny County Police Bomb Squad said its EOD and K9s conducted a sweep of the "plane, passengers, and luggage with negative results."
The county bomb squad said the incident has since been cleared.
PIT airport officials said passengers have been rebooked and are on another aircraft. They will continue to their destination.
Pittsburgh International Airport said in a statement that "safety and security are always a top priority," further saying "Crews and law enforcement have cleared the scene at PIT" and that the "aircraft screened negative."
It is unclear what officials were looking for aboard the plane.
No further details on this incident have been released.
https://www.wtae.com/article/flight-diverted-pittsburgh-possible-security-issue/71060622
United plane forced to evacuate over bomb threat at Denver airport, the second scare in days
By Chris Bradford
A United Airlines plane with around 200 passengers on board was forced to evacuate over a bomb threat at Denver airport – the second such security scare in a matter of days.
Travelers bound for Washington Dulles disembarked the plane Sunday night while the jet was screened over a “security concern,” a United Airlines spokesperson told 9News.
Footage, obtained by Storyful, showed cop cars surrounding the jet and emergency crews standing on steps by the plane’s doors.
A United Airlines plane with around 200 passengers on board was forced to evacuate over a bomb threat at Denver airport – the second such security scare in a matter of days.
Travelers bound for Washington Dulles disembarked the plane Sunday night while the jet was screened over a “security concern,” a United Airlines spokesperson told 9News.
Footage, obtained by Storyful, showed cop cars surrounding the jet and emergency crews standing on steps by the plane’s doors.
The scare came just a day after a United Airlines flight heading to LaGuardia was diverted to Pittsburgh over fears of a potential bomb on board.
“We are going to have to start treating this as a potential bomb… we are going to need to go and start a diversion and get things settled. It’s a beeping noise, sequential, one beep per second,” a crew member said, in audio posted to liveatc.com.
The Boeing 737‘s 159 passengers and 6 crew members exited the plane safely via slides and no injuries were reported, a United representative told The Post in a statement.
The Pittsburgh FBI bomb technicians and Special Agents, local police and the Allegheny County bomb squad were dispatched to the scene to investigate, WCVB reported.
The Allegheny County Police Bomb Squad told the outlet its Explosive Ordinance Disposal team and bomb sniffing dogs conducted a sweep which had “negative results” for bombs.
“Our EOD team and K9s conducted a sweep of the aircraft, passengers and luggage with negative results,” the department told the outlet.
https://nypost.com/2026/04/20/us-news/united-plane-forced-to-evacuate-over-bomb-threat-at-denver-airport-the-second-scare-in-days/
'Everyone is safe' after small plane crash-lands at Ojo Santa Fe Spa Resort
By Nicholas Gilmore
Both people on board got out safely after a small plane bound for Taos crash-landed Friday morning at a resort in La Cienega just after taking flight in Santa Fe.
Officials said the single-engine Cirrus SR22 lost power and then deployed a parachute, allowing it to descend to the ground at Ojo Santa Fe Spa Resort. It came to rest on some trees and shrubs next to a building.
While no one was seriously injured in the incident, it raised concerns among some residents in the community about their close proximity to the growing Santa Fe Regional Airport.
“People are concerned about the safety of air traffic,” said Santa Fe County Commissioner Camilla Bustamante, a La Cienega resident, noting a previous crash ended in tragedy. “The last one was just a few years ago — so we’ve had two crash landings in La Cienega.”
Bustamante said she heard a loud boom when the plane crashed near her residence around 10 a.m. Friday. She called into the emergency dispatch center minutes after the crash.
New Mexico State Police, which opened an investigation into Friday’s crash, said in a statement the plane “clipped” the side of a building when it landed, but reports indicated it did not cause significant damage to any structures.
The pilot and a passenger got out after the plane touched down, according to reports. One of them was taken to a local hospital with complaints of back pain.
The registered owner of the plane is a White Rock man who heads a Los Alamos-based technology consulting firm, according to Federal Aviation Administration records. He did not return calls seeking comment Friday.
The Cirrus SR22 is equipped with an “airframe parachute system” that can be deployed from the aircraft, according to the manufacturer.
The FAA and the National Transportation Safety Board are also conducting an investigation into the incident. The agencies are expected to release a preliminary accident report within 30 days.
A spokesperson for the National Transportation Safety Board said information the agency has received so far indicates the plane “experienced a reported loss of power.”
“During the on-scene phase of the investigative process, the NTSB does not determine or speculate about the cause of the accident,” the agency said in a statement.
A helicopter could be seen flying over Ojo Santa Fe Spa Resort shortly before noon Friday with emergency responders still at the scene. The small white plane — mostly intact — was sitting next to a casita toward the back of the resort. The plane appeared to have come down close to a dirt road near the southern end of the property.
Officials at the resort declined to comment or provide information about the incident Friday. An employee who answered the phone said only that “everyone is safe.”
A dispatch report provided by the Santa Fe Regional Emergency Communications Center states several calls came in with reports of the crash Friday morning, the first at 9:54 a.m.
The Santa Fe County Sheriff’s Office and fire department arrived at the scene, as well as state police.
Officers indicated in the dispatch report there was “no fire” and “no hazard,” and that the passengers had “self-extracted” from the aircraft.
However, an officer noted in the report the plane was
leaking “quite a bit of fuel.”
City of Santa Fe spokesperson Peter Olson said some airport staff were sent to the scene to aid federal investigators, and the city offered to send its aircraft rescue and firefighting vehicles, which are kept at the airport, but they weren’t needed.
The incident follows a fatal plane crash in La Cienega in July 2023.
A surgeon from Los Angeles was the pilot and sole occupant of a Cessna that crashed into a home shortly after taking off from the Santa Fe airport, causing a massive explosion that engulfed the home in flames.
That crash was caused by catastrophic engine failure, according to an accident brief from the FAA, which states “the investigation determined the left engine failed after takeoff.”
A resident of nearby La Cieneguilla, Jose Villegas, said the surrounding area has been impacted by the airport’s expansion, a yearslong project that is still underway.
“As the airport expands, more little planes will be flying in and out of that facility,” he said, noting he believes there could be more crashes.
“Even though the city does its emergency training, we haven’t had to deal with a large plane crash here,” he said, adding, “Thank God no one was hurt.”
Pilot injured after plane crashes in Ardmore
By Austin Hedgcoth and KXII Staff
ARDMORE, Okla. (KXII) - A small passenger plane crashed in Ardmore at the Downtown Executive Airport Friday afternoon.
Chris McMurray, who works in airport operations, heard
an airplane land about 2 p.m., even though no pilots had called in on approach.
“I went outside just to inspect and I thought I saw what was the tail of an airplane off the runway sitting in the ditch,” McMurray said.
His eyes did not deceive him—a crash is exactly what he saw.
The twin-engine Piper skidded off the end of the runway, ran through a grassy field and smashed into the barrier fence at the north end of the airport.
“When we see an accident like that that’s happened, we want to be sure first that the pilot and passengers are okay,” McMurray said.
Fortunately, this time, everyone aboard was alright. The pilot had minor injuries, and the three passengers were not hurt.
Nearby neighbors told KXII 12 News that they heard a strange sound, and when they looked outside, they saw the plane bounce off the runway before skidding into the barrier fence.
McMurray said the gusty southern breeze, coupled with the pilot’s decision to land with the wind—not against it as is protocol—spelled trouble.
“We were just real happy to know that the pilot and the passengers were okay,” McMurray said. “That’s the main thing.”
McMurray has seen a lot during his career working in aviation, but he said this was a first.
“I’ve never dealt with this before, so it’s a first for me,” he said.
By Friday night the airport had reopened and the FAA had begun its investigation. The plane will be moved to an off-airport location where it can be further inspected.
Flight tracking website FlightAware showed that the flight took off from Hot Springs Arkansas.
Small plane flying from California lands in Auburn construction site after losing engine
by KOMO News Staff
AUBURN, Wash. — A small aircraft made an emergency landing in Auburn Saturday afternoon after experiencing engine trouble while en route from California, according to Auburn police.
During the flight, the pilot initially attempted to land in Renton but determined it would be safer to divert to Auburn.
As the plane approached the area, it lost its second engine, forcing an emergency landing.
The female pilot successfully landed the aircraft in a field at a GSA construction site. She sustained non-life-threatening injuries and was transported for medical evaluation.
Another male passenger on board was not injured, according to police.
Emergency responders arrived quickly and secured the area. The incident remains under investigation.
https://komonews.com/news/local/small-plane-from-california-makes-emergency-landing-in-auburn-field-construction-site-after-engine-trouble-pilot-hurt
Emergency crews respond to aircraft accident near Daniel Field Airport
Darasha Singleton
AUGUSTA, Ga. (WFXG) - The Richmond County Sheriff’s
Office and Augusta Fire Department are on the scene of an aircraft accident at Daniel Field Airport.
According to law enforcement, deputies found a single-engine plane that had overshot the runway and crashed into a fence shared by the airfield and The Patch.
No injuries have been reported, as the pilot was found at the scene and declined medical treatment. No additional injuries have been reported.
Emergency Crews Respond to Small Plane Crash in Ironton
By Jeremy Newman
IRONTON, OH — Local authorities are on the scene of a
small aircraft crash that occurred Friday afternoon in Lawrence County.
Emergency dispatchers confirmed that the aircraft went down on County Road 1A in Ironton at approximately 2:00 p.m. Multiple fire and rescue crews were immediately deployed to the area to secure the scene.
Preliminary Details
Initial reports from Lawrence County Dispatch indicate that only one person—the pilot—was on board the aircraft at the time of the incident. The current condition of the pilot has not yet been released, and the identity of the individual is being withheld pending family notification.
Images from the area show first responders cordoning off a section of the roadway, which remains closed to traffic as investigators begin their work.
Federal Investigation Pending
The cause of the crash remains unknown. Following standard protocol for aviation incidents, both the Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) have been notified.
Federal investigators are expected to arrive on-site within the next 24 hours to begin a formal probe into the mechanics of the flight and the circumstances leading up to the crash.
https://www.sciotopost.com/emergency-crews-respond-to-small-plane-crash-in-ironton/
Four killed in plane crash near Union County Airport
by: Isabel Martin
UNION COUNTY, S.C. (WSPA) — Four people were killed in a plane crash near the Union County Airport on Friday.
Officials said they responded to the scene on Airport Road just after 6 p.m. after dispatch received reports of a plane that has possibly crashed and large amounts of black smoke were seen in the area.
The Union County Sheriff’s Office, the Southside Fire Department, and the South Carolina Forestry Commission responded to the crash.
Investigators said a single-prop plane was located crashed in the trees. Forestry workers helped clear the trees from the crash site.
According to the Union County Coroner’s Office, four people were on board the plane. All four were killed in the crash. The identities of the passengers are still being confirmed and will be released after their families have been notified.
The coroner’s office said the plane had stopped in Union to refuel.
Investigators said they are working to pinpoint details about the plane involved in the crash.
Additionally, the airport has temporarily been shut down. Deputies asked that the public avoid the area while emergency crews respond to the crash.
The crash remains under investigation. The Federal Aviation Administration and the National Transportation Safety Board have been notified of the crash.
“The engine stopped and it crashed”: The dramatic account from neighbors after the plane crash in Minga Guazú
The crash of the small plane carrying valuables in Minga Guazú, Alto Paraná Department, not only left a tragic toll, but also scenes of despair, bravery and total loss, according to neighbors who witnessed the moment of impact and participated in the rescue of the survivors.
By Wilson Ferreira
Luciano Galeano, a resident of the Minga Guazú area, Alto Paraná Department, was one of the first witnesses of the plane crash and his account reconstructs the seconds before the plane, which had four crew members, went down.
“I saw the plane very low. The engine stopped and it came straight down,” he said, describing an uncontrolled maneuver that ended in tragedy.
After the impact, the situation became chaotic. “Then we arrived to see what happened. The plane crashed and immediately burst into flames,” he said.
Amid the smoke, flames, and wreckage of the aircraft, cries for help began to be heard.
“One of the occupants shouted to us: ‘Help!’ My wife and I went to help them. ‘Help,’ he kept saying. They were trapped,” recalled Galeano, who did not hesitate to approach, despite the imminent risk.
The fire was advancing rapidly and the danger of explosion was ever-present.
“I went into the middle of the fire to get them out. One of them told us not to go in, that it was going to explode. The fire was huge,” he recounted, revealing the tension of the moment.
Despite the danger, they managed to rescue the occupants. According to Galeano, a woman, part of the crew, was pulled out unconscious. “We got her out quickly,” he stated.
The neighbors acted before the arrival of the emergency teams.
“The firefighters arrived later, when the plane had practically already burned and after we had already gotten everyone out,” the local added.
House damaged by the small plane
The accident affected not only the occupants of the aircraft but also bystanders. The small plane crashed near a house, which was severely damaged.
Basílica Duarte, owner of the affected house, said that she was not at the location at the time of the incident.
“This is our house. We went to the store to do some shopping. When we came back, there were already a lot of people, everything had already happened,” she said.
The woman explained that they did not hear the impact because they were outside the house.
“We went out to the road to buy something and we didn’t hear anything. We lost everything,” he lamented, describing the damage suffered in his home.
The scene afterward was devastating: charred remains of the aircraft, a damaged house, and neighbors trying to come to terms with what had happened.
Between improvised heroism and material loss, the community was marked by an episode that transformed an ordinary afternoon into a tragedy.
While investigations into the causes of the accident continue, the testimonies of those who were there help to understand the magnitude of the event.
The pilot of the aircraft, General Fernando Noldin, lost his life in this air accident.
The co-pilot Yeruti Nuñez, and the Prosegur company escorts, Hirán Bogado and Fredy Recalde, survived.
https://www.ultimahora.com/el-motor-paro-y-cayo-el-dramatico-relato-de-vecinos-tras-la-tragedia-aerea-en-minga-guazu
NTSB Final Report: Piper PA-22-108
The Pilot Reported That The Elevator Became Jammed In A Nose-Up Attitude After It Struck (A) Sign
Location: Colorado Springs, Colorado Accident Number: CEN26LA053
Date & Time: November 26, 2025, 10:57 Local Registration: N4588Z
Aircraft: Piper PA-22-108 Aircraft Damage: Substantial
Defining Event: Loss of control on ground Injuries: 2 None
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot reported that during he felt a gust of wind from the left that lifted the left wing. The pilot stated that he overcorrected, the airplane became unstable, and he decided to perform a go-around. After the pilot initiated the go-around, the airplane veered to the right of the runway, struck a runway distance remaining sign, and then became airborne. The pilot reported that the elevator became jammed in a nose-up attitude after it struck the sign. The airplane reached an altitude of about 400 ft above ground level before the pilot regained control and returned to land without further incident. During the accident sequence, the airplane sustained substantial damage to the left wing strut, elevator, and horizontal stabilizer.
The pilot reported that there were no preimpact mechanical malfunctions or failures with the airplane that would have precluded normal operation. The pilot further reported that the accident could have been prevented if he had established better directional control before initiating the go-around.
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.
FMI: www.ntsb.gov
NTSB Prelim: Robinson Helicopter Company R44 II
The Purpose Of The Flight Was To Use The Helicopter To Flush Wildlife Into An Open Pasture
Location: Stonewall, TX Accident Number: CEN26LA148
Date & Time: March 24, 2026, 09:30 Local Registration: N233JD
Aircraft: Robinson Helicopter Company R44 II Injuries: 2 Serious
Flight Conducted Under: Part 91: General aviation - Aerial observation
On March 24, 2026, about 0930 central daylight time, a Robinson R44 II helicopter, N233JD, was substantially damaged when it was involved in an accident near Stonewall, Texas. The pilot and passenger were seriously injured. The helicopter was operated as a Title 14 Code of Federal Regulations Part 91 aerial observation flight.
According to the pilot, she conducted a normal preflight inspection of the helicopter and found no anomalies. She stated that the purpose of the flight was to use the helicopter to flush wildlife into an open pasture for observation. While in a hover, about 15 to 30 ft above the tree line, she heard a loud “pop” and felt the helicopter jerk. The helicopter immediately entered an uncontrolled descent into terrain. The pilot reported that the helicopter would not respond to inputs made with the anti-torque pedals.
The pilot, passenger, and a witness reported hearing a loud “pop” from the helicopter before the sound of the engine went quiet. According to the passenger, the helicopter shook violently after the “pop” was heard and then rotated rapidly in a clockwise direction.
The helicopter sustained substantial damage to the fuselage, the main rotor system, the tailboom, and the tail rotor system. The helicopter was recovered to a secure facility for further examination.
FMI: www.ntsb.gov
NTSB Final Report: Piper Aircraft Inc PA 46-350P
Pilot’s Encounter With Convective Weather Conditions, Which Resulted In A Loss Of Airplane Control
Location: Hartsburg, Missouri Accident Number: CEN24FA160
Date & Time: April 16, 2024, 12:05 Local Registration: N451MA
Aircraft: Piper Aircraft Inc PA 46-350P Aircraft Damage: Destroyed
Defining Event: Loss of control in flight Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The airplane was on an instrument flight rules flight and air traffic control (ATC) provided the pilot with vector guidance to avoid an active military operations area (MOA). The controller informed the pilot that he would only be able to deviate to the left of his course due to the active MOA. At that time, the airplane was in an area of developing convective weather activity and likely in instrument meteorological conditions. The pilot reported to ATC that he encountered freezing rain. ATC communications revealed that the pilot requested to deviate to the left of his course due to weather, including mention of encountering freezing rain, which ATC approved. Flight track data showed the airplane entered a descending left turn. A performance study based on the aircraft track data showed that, during the turn, the airplane’s roll angle reached 70°, the pitch angle reached -17° and then -34°, and the calibrated airspeed exceeded both the airplane's published never exceed speed (VNE), and its maximum operating maneuvering speed (VO). During the turn, the airplane’s structure broke apart, and wreckage was distributed along a 3-mile path. The flight path depicted in the flight track data was consistent with a loss of airplane control.
Postaccident examination of the airplane confirmed that the horizontal stabilizer and the wings failed in a downward direction. A failure of the airplane’s horizontal stabilizer would result in the airplane pitching forward and a high negative load to the wings. The examination noted that all identified failures in the airplane structure had signatures consistent with overload failure. Examination of the airplane’s flight control system did not reveal any preexisting anomalies. The cockpit avionics could not be tested due to impact damage.
Based on the available data, the pilot encountered forecast adverse weather associated with convective activity. The pilot noted to ATC that he encountered freezing rain, however, the quantity of ice accumulation and its effect on the flight could not be determined. While attempting to deviate from his flight path to avoid this weather, airplane control was lost and it entered a steep descending turn. During the turn, the airplane’s speed exceeded its published never exceed speed, which resulted in overload failure of the horizontal stabilizer and subsequent failure of the airplane’s wings.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s encounter with convective weather conditions, which resulted in a loss of airplane control, the exceedance of the airplane’s never exceed speed, and the resulting overload failure of the horizontal stabilizer and subsequent failure of the airplane’s wings.
FMI: www.ntsb.gov

Today in History
14 Years ago today: On 20 April 2012 Bhoja Airlines flight 213, a Boeing 737-200, crashed after encountering windshear while on approach to Islamabad Airport, Pakistan, killing all 127 occupants.
| Date: | Friday 20 April 2012 |
| Time: | 18:40 |
| Type: | Boeing 737-236A |
| Owner/operator: | Bhoja Airlines |
| Registration: | AP-BKC |
| MSN: | 23167/1074 |
| Year of manufacture: | 1984 |
| Total airframe hrs: | 46933 hours |
| Cycles: | 37824 flights |
| Engine model: | P&W JT8D-15A |
| Fatalities: | Fatalities: 127 / Occupants: 127 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | 4,2 km SE of Islamabad-Benazir Bhutto International Airport (ISB) - Pakistan |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Karachi-Jinnah International Airport (KHI/OPKC) |
| Destination airport: | Islamabad International Airport (ISB/OPRN) |
| Investigating agency: | PakCAA |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
Bhoja Airlines flight 213, a Boeing 737-200, crashed after encountering windshear while on approach to Islamabad Airport, Pakistan, killing all 127 occupants.
Bhoja Airlines flight B4213 departed Karachi (KHI) at 17:05 on a domestic flight to Islamabad (ISB). This was the inaugural evening flight for the airline on this route.
The flight climbed to a cruising altitude of FL310 and continued towards Islamabad. Weather at the destination was poor due to a passing thunderstorm. At 18:19 the captain at a distance observed the squall line. Moments later the flight was cleared to descend to FL200. During the descent the captain and first officer discussed the weather. They were worried about the severity of the thunderstorm ahead.
At 18:26 the first officer contacted Islamabad Approach and received clearance for the One Foxtrot arrival for an ILS approach to runway 30. After receiving further descent clearance the first officer discussed opportunities to approach the airfield through a gap in the squall line. The Approach controller gave radar vectors and descent instructions to fly through the gap in the storm.
At 18:35, Islamabad Approach gave a weather update and said "Bhoja 213 surface wind at Islamabad ah is varying between 180° to 270°, 10 kts and ah sometimes gusting to 20 kts and runway condition is wet, light drizzle is ah uhm going on, braking action not known".
Two minutes later the airplane entered the squall line. Although the Bhoja Air Operational Manual prohibited flight in these conditions, the captain decided to continue. The airplane was configured for the approach with flaps and slats selected and the undercarriage was down. The first officer then reported the speed to be 220 knots, which was 30 knots higher than the recommended speed. The captain reacted surprised as he did not expect this because the he was flying with the auto-throttle engaged. Likely the increase in speed was a result of windshear. The aircraft then entered the active weather cell with precipitation continuing in varying intensity. At 18:39 the airplane captured the ILS and descended on the glide slope. At this point the aircraft should have been in landing configuration with flaps at 30°. However, only flaps 5 were selected.
The aircraft then encountered an increasing downdraft. The pitch attitude increased and computed airspeed decreased as the autopilot attempted to maintain the glide slope. The GPWS consequently sounded with the aural alarm: "Wind shear - Wind shear - Wind shear". Although the first officer anxiously called for a go around, no action was taken.
The downdraft dissipated and the pitch attitude decreased but the aircraft deviated left of the extended runway centerline, and was brought back by the captain. At that moment the autopilot disconnected due to the aircraft deviation beyond the autopilot maximum authority limits. The auto throttle remained engaged in IAS speed mode. Following autopilot disconnect, there was no control wheel activity recorded for approximately 6 seconds and no control column activity for approximately 8 seconds. The crew were likely confused. During this period of control inactivity, the aircraft deviated below the glide slope.
Then the Terrain Awareness Warning System (TAWS) alarm sounded: "Whoop, Whoop, Whoop". No action was taken by either crew member. A few seconds later the aircraft entered another downdraft and the rate of descent increased rapidly. The TAWS alarm sounded again, directing the crew to "pull up". The captain responded with a nose-up column input. However, pressure altitude and thrust continued to decrease. The downdraft dissipated rapidly, resulting in a rapid increase in angle of attack of the aircraft, which activated the stick shaker for almost 2 seconds. It appeared that captain lowered the nose down to get out of stick shaker regime however, proper and complete Boeing recommended stall and recovery procedures were not carried out. This resulted in a 12° nose down pitch. Then another windshear alarm sounded, followed by another stick shaker activation. The first officer shouted to "get out" and "go around" but the attempts by the captain failed as he did not apply the proper procedures to execute a go around.
Shortly after initial ground contact, the aircraft struck a steeply sloped terrace about 5 meters high which resulted in significant structural breakup of the aircraft structure.
The ineffective automated flight deck management in extreme adverse weather conditions by cockpit crew caused the accident. The ineffective automated flight deck management was due to various factors including; incorrect selection of cockpit crew on account of their inadequate flying experience, training and competence level for Boeing 737-236A (advanced version of Boeing 737-200 series), absence of formal simulator training in respect of FO for handling an automated flight deck, non-existence of cockpit crew professional competence / skill level monitoring system at operator level (Bhoja Air).
The cockpit crew incorrect decision to continue the flight for destination and non-adherence to Boeing recommended QRH and FCOM remedial actions /procedures due to non-availability of customized aircraft documents (at Bhoja Air) for Boeing 737-236A (advanced version of Boeing 737-200 series) contributed towards the causation of accident. The inability of CAA Pakistan to ensure automated flight deck variance type training and monitoring requirements primarily due to incorrect information provided by the Bhoja Air Management was also a contributory factor in causation of the accident.
METAR:
13:00 UTC / 18:00 local time:
OPRN 201300Z 23020KT 4000 TS FEW025CB SCT030 BKN100 25/15 Q1009.3/29.80
14:00 UTC / 19:00 local time:
OPRN 201400Z 23020KT 3000 TSRA FEW025CB SCT030 BKN100 20/16 Q1011.0/29.85
