Skip to content

Thursday the 5th of March, 2026

The following are your stories for today...

Be safe out there!

Tom

-

Small Plane Goes Down Just North Of Chevy Chase Country Club

By Journal Staff

Emergency responders rushed to the scene of a small plane crash in unincorporated Deerfield, north of Chevy Chase Country Club in Wheeling, just after 9:45 p.m. Wednesday.

Yellow tape blocked the street on the 800 block of Swallow, located west of Milwaukee Avenue and north of Lake Cook Road in the Inverrary Lane area. A single-engine aircraft went down in a backyard and suffered heavy damage.

The incident location is about a mile north of Chicago Executive Airport.

A resident who lives five houses away told a Journal & Topics reporter at the scene that the plane “skidded” through more than one backyard before coming to a stop, with its propeller getting stuck in the side of a home on Swallow. No smoke or fire was seen, the resident said, and there were no obvious calls for help from the plane. The resident reported hearing a “loud crash” sound.

Initial reports were that one individual was on board the plane, but their status is unknown. Reports have yet to be verified with officials. North Shore Gas also responded to the scene due to a natural gas leak behind a home on Swallow.

Small Plane Goes Down Just North Of Chevy Chase Country Club

3 hurt after plane crashes in north Phoenix neighborhood

Pilot instructor, student and a homeowner are all expected to be OK

By Alexis Cortez

PHOENIX (AZFamily) —Three people are injured after a plane went down and crashed into a north Phoenix neighborhood early Wednesday morning.

A Federal Aviation Administration (FAA) spokesperson said just before 7:30 a.m., a Piper PA-28 crashed into a neighborhood near Cave Creek Road and Deer Valley Drive on its way back to Deer Valley Airport. Two people were on board the plane at the time of the crash.

Arizona’s Family obtained video from a neighbor that shows the plane just seconds before it takes a dive and slams into two homes.

“I said, ‘Daddy I think I saw a plane crash!’,” said 9-year-old Brianna, a neighbor. “I was a little scared because I was hoping that everyone was OK.”

“I was backing out, getting ready to take her to school, backing out of my driveway and she looked over to her left and said ‘Daddy I just saw a plane go down’ and I just didn’t believe it because I didn’t see any smoke and I told her, you know, there’d be a big mushroom fire or cloud of smoke out there and there was nothing and so I proceeded to take her to school like nothing was wrong,” said the girl’s father, Sean.

“It wasn’t until I got about halfway home after dropping her off at school, I looked at a clip online and it was real. So, it’s been an out of body experience,” Sean added.

Phoenix Fire Capt. Todd Keller said the pilot instructor and student were hospitalized in stable condition. Keller said both sustained minor cuts and burns, but were alert while being treated.

“It hit two houses. Fortunately, everyone was okay. Situations like this when you do have multiple residences involved and you have houses with people coming and going, it is a miracle that no one was injured,” Capt. Keller explained.

A homeowner was also hospitalized, but is expected to be OK. No firefighters were injured during the response.

“Early indications are that the plane did hit that first house, landed in that second house’s backyard. That first house person is being transported for precautionary measures,” Capt. Keller said.

Arizona’s Family news chopper witnessed a plane with its nose down into a backyard. Two homes sustained damage, and bits of debris were scattered across one backyard. A piece of the aircraft was also on a roof.

“The pilots were able to get out of the cockpit and were resting up against the outdoor kitchen. They were able to walk, but definitely bloodied and disoriented. There was a strong presence of jet fuel and that could have ignited at any time. So, we just made sure that they got across the street and into safety and then from there we just offered up our house for their family because they have a 4-month-old baby and then let the dogs roam around the backyard,” said Mychal Hammonds, a neighbor. “I wouldn’t say hero. I’m just trying to help out, nothing special.”

The American Red Cross disaster action teams are working with families impacted by the crash and providing assistance.

Details remain limited as to what led up to the crash.

Arizona’s Family has also reached out to the National Transportation Safety Board (NTSB).

“Everybody’s OK and that’s the main part, but it is a concern being a resident in this neighborhood. As you see there are many houses near us and the training flight path goes directly over us constantly. So, it is concern and unfortunately today it did happen,” said Claire St. Pierre, a neighbor.

https://www.azfamily.com/2026/03/04/3-hurt-after-plane-crashes-north-phoenix-neighborhood/

Shree Airlines aircraft suffers tire burst in Surkhet

Himal Press

SURKHET: A Shree Airlines aircraft suffered a tyre burst while landing at Surkhet Airport on Wednesday.

According to Hirajan Kafle, chief of Civil Aviation Office Surkhet, the Dash 8-Q400 aircraft with call sign 9N-AOL experienced a puncture in its left rear tyre during landing. The incident occurred right after the plane touched down on the runway, he added.

All passengers on board disembarked safely, and no injuries were reported.

“The aircraft has been moved to the parking bay. The airline is sending a technical team from Kathmandu for repairs,” he added.

Following the accident, the airline has canceled its Surkhet–Kathmandu flight.

https://en.himalpress.com/shree-airlines-aircraft-suffers-tire-burst-in-surkhet/

Military helicopter makes emergency landing in Berks County

By Brendan Brightman

A military helicopter made an emergency landing in a field in Robeson Township in Berks County on Wednesday, police said.

The helicopter landed just after 1 p.m. in the area of rea of Moyer Road and Weaver Road after a fire light indication activated in the cockpit, police said.

According to police, the helicopter landed out of an abundance of caution and no injuries were reported due to the incident.

Photos shared with NBC10 showed the helicopter still in the field on Wednesday afternoon:

The incident is being investigated by the appropriate authorities, police said.

https://www.nbcphiladelphia.com/news/local/military-helicopter-emergency-landing-berks-county/4363274/

NTSB Final Report: Embraer ERJ 170-100

Flight Crew’s Decision To Continue The Approach Without The Correct Ils Frequency Was Likely Affected By Their Task Saturation And Planned Continuation Bias

Location: Chicago, Illinois Incident Number: DCA24LA318
Date & Time: September 25, 2024, 15:26 Local Registration: N772MR
Aircraft: Embraer ERJ 170-100 LR Aircraft Damage: None
Defining Event: Wrong surface or wrong airport Injuries: 68 None
Flight Conducted Under: Part 121: Air carrier - Scheduled

Analysis: This incident occurred when the flight crew of Envoy Airlines flight 3936 (ENY3936), an Embraer 170-100 LR, was cleared for a visual approach to land on runway 10C at Chicago O’Hare International Airport (ORD), Chicago, Illinois, however, the flight crew inadvertently landed on runway 10L.

While on descent and upon initial check-in with the ORD approach controller, the flight crew was instructed to expect runway 10C. They were subsequently cleared for the instrument landing system (ILS) to runway 10C. The flight crew acknowledged and correctly read back the approach clearance. The flight crew stated that the captain, who was the pilot monitoring, briefed the approach, programmed the flight management computer (FMC) with the ILS approach to runway 10C to back up the planned visual approach. However, they were not receiving the ILS identifier. The captain attempted to troubleshoot why the localizer frequency would not autotune by reloading the approach in the FMC and manually tuning the frequency. Unable to resolve the issue they elected to proceed visually.

The captain contacted the air traffic control tower (ATCT) controller stating they were on the visual approach to runway 10C, and the airplane was cleared to land on runway 10C. However, the airplane was aligned with and landed on runway 10L. The flight crew’s decision to continue the approach without the correct ILS frequency was likely affected by their task saturation and planned continuation bias, and their inability to perceive and efficiently integrate available information.

Planned continuation bias is an unconscious cognitive phenomenon to continue with the original plan in spite of changing conditions. Once a plan is made and committed to, it becomes increasingly difficult for stimuli or changing conditions to be recognized as necessitating a change to the plan. In addition, as workload increases conditions that may appear obvious to individuals external to the situation are difficult for people caught up in the plan to recognize.

Recorded data from the flight data recorder revealed that while flying a heading to intercept the ILS 10C, the localizer frequency in the Nav 1 radio was correctly tuned to 108.95 MHz, the frequency for the ILS 10C localizer, for four seconds. Subsequently, the Nav 1 radio was changed to 108.4 MHz and Nav 2 radio was changed to 113.0 MHz for the remainder of the flight. Although the correct ILS frequency (108.95 MHz) was briefly tuned in the Nav 1 radio, it was subsequently changed to an incorrect frequency (108.4 MHz), and Nav 2 was tuned to a non-ILS frequency (113.0 MHz), preventing the crew from confirming alignment with runway 10C.

The FAA mandatory occurrence report (MOR) revealed that the ATCT controller noticed the runway alignment error and coordinated with the runway 10L controller to allow ENY3936 to land on the incorrect runway as no traffic conflicts were noted. The air traffic control (ATC) services provided by the controller were deficient and contrary to FAA directives. Specifically, the controller failed to notify ENY3936 of their alignment error and did not issue control instructions to prevent the wrong surface landing. Had the controller notified the flight crew of the alignment error or provided control instructions it is likely that the wrong surface landing would have been prevented.

Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this incident to be -- The flight crew’s misidentification of the intended landing runway, which resulted in an approach to and landing on the wrong runway due to their planned continuation bias. Contributing to the incident was the flight crew’s decision to continue the approach without the correct ILS frequency in the FMS. Also contributing was air traffic control’s failure to notify the flight crew that the were lined up with the incorrect runway contrary to FAA directives.

FMI: www.ntsb.gov

Today in History

60 Years ago today: On 5 March 1966 BOAC flight 911, a Boeing 707-400, crashed near Mount Fuji, Japan, after encountering severe turbulence killing all 124 occupants.

Date: Saturday 5 March 1966
Time: 14:15
Type: Boeing 707-436
Owner/operator: British Overseas Airways Corporation - BOAC
Registration: G-APFE
MSN: 17706/113
Year of manufacture: 1960
Total airframe hrs: 19523 hours
Cycles: 6744 flights
Engine model: Rolls-Royce Conway 508
Fatalities: Fatalities: 124 / Occupants: 124
Other fatalities: 0
Aircraft damage: Destroyed, written off
Category: Accident
Location: Mount Fuji -    Japan
Phase: En route
Nature: Passenger - Scheduled
Departure airport: Tokyo-Haneda Airport (HND/RJTT)
Destination airport: Hong Kong-Kai Tak International Airport (HKG/VHHH)
Confidence Rating:  Accident investigation report completed and information captured

Narrative:
BOAC flight 911, a Boeing 707-400, crashed near Mount Fuji, Japan, after encountering severe turbulence killing all 124 occupants.

BOAC Flight 911 was a scheduled service from San Francisco (SFO) to Hong Kong (HKG) via Honolulu (HNL) and Tokyo (HND). The Boeing 707 was expected to arrive at Tokyo Airport at 16:45 on 4 March. However, due to poor meteorological conditions at Tokyo and because the precision approach radar (PAR) of the GCA was out of service, it diverted to Fukuoka (FUK) and landed there at 18:00. After staying overnight at Fukuoka, Flight 911 left for Tokyo at 11:25 and landed there at 12:43. The aircraft was prepared for the next leg to Hong Kong and a flight plan was filed for a flight in accordance with the instrument flight rules via Oshima on airway JG6 to Hong Kong at FL310.
At 13:42 hours the crew contacted ATC requesting permission to start the engines and clearance for a VMC climb via Fuji-Rebel-Kushimoto. The aircraft left the ramp at 13:50. It was instructed to make "a right turn after take off", and departed Tokyo Airport at 13:58. After takeoff the aircraft flew over Gotemba City on a heading of approximately 298 deg at an altitude of approximately 4900 m and indicated airspeed of 320 to 370 knots. The aircraft, trailing white vapor, then suddenly lost altitude over the Takigahara area, and parts of the aircraft began to break away over Tsuchiyadai and Ichirimatsu. Finally over Tarobo at an altitude of approx. 2000 m, the forward fuselage broke away. The mid-aft fuselage together with the wing, making a slow flat spin to the right, crashed into a forest at the foot of Mount Fuji. The forward fuselage crashed into the forest approx. 300 m to the west of the above site and caught fire.

PROBABLE CAUSE: "The aircraft suddenly encountered abnormally severe turbulence over Gotemba City which imposed a gust load considerably in excess of the design limit."

Scroll To Top