Here are the stories for today...
Be safe out there!
Tom
--
Small plane crash kills pilot in Sweden, Maine
The Federal Aviation Administration says a Cessna 182 crashed in Sweden, Maine around 3:45 p.m.
Author: NEWS CENTER Maine Staff
SWEDEN, Maine — A pilot was killed in a small plane
crash in Sweden Maine around 3:45 p.m., according to the Oxford County Sheriff's Office.
The pilot has been removed and is being transported to Augusta for an autopsy.
The road will be closed for the night, and the Federal Aviation Administration and National Transportation Safety Board is set to investigate in the morning.
Only the pilot was on board, according to the FAA.
https://www.newscentermaine.com/article/news/local/small-plane-crashes-in-sweden-maine-faa-says/97-d3262c1d-a974-4e19-81e8-e73c8f0cb70d
Pilot avoids Hill City Elementary School before Pickens County plane crash
By FOX 5 Atlanta Digital Team
The Brief
-
- A pilot avoided Hill City Elementary School before crashing a small plane into a Pickens County field near Highway 53 West on Monday afternoon.
-
- Both people aboard the aircraft escaped with minor, non-life-threatening injuries and were taken for medical evaluation and treatment.
-
- The Federal Aviation Administration and the National Transportation Safety Board are investigating what caused the crash.
PICKENS COUNTY, Ga. - A pilot steered a troubled small
plane away from Hill City Elementary School and into a rural Pickens County field near Highway 53 West on Monday afternoon, leaving both people aboard with minor injuries.
Pickens County plane crash
What we know:
Deputies with the Pickens Sheriff's Office, alongside Pickens Fire and EMS, responded to a call of an airplane crash around 1:40 p.m. Monday. First responders located the downed small plane in a big open field near Highway 53 West and Woodstock Church of Jasper.
Pilot avoids elementary school
What they're saying:
Pickens Sheriff's Office Capt. Chris Leake credited the
pilot with recognizing an emergency and deliberately steering clear of nearby Hill City Elementary School.
"We have a school that's just kind of right over there, and they were able to avoid that and come over here into this big open field. So we're very grateful to the pilot for recognizing the area that he was in and trying to land in a safe area away from some of our critical structures being the Hill City Elementary School over there," Leake said.
"We're very grateful to the pilot for recognizing that there was an issue and avoiding the school and we're also grateful that pilots and the co-pilot didn't receive major injuries and we anticipate the FAA and NTSB doing the follow-up investigation to figure out exactly what happened and keep our airways safe," Leake added.
Crash injuries and transport
By the numbers:
Two occupants—identified by deputies as the pilot and co-pilot—were inside the aircraft when it went down. Both suffered minor, non-life-threatening injuries and were transported from the scene for evaluation and treatment.
Federal aviation crash investigation
What we don't know:
Authorities have not yet confirmed what caused the plane to crash or released the identities of the two people on board. Officials also have not confirmed whether anyone on the ground was injured. The Pickens Sheriff's Office has turned the scene over to the Federal Aviation Administration and the National Transportation Safety Board to conduct follow-up investigations.
https://www.fox5atlanta.com/news/small-plane-crashes-near-jasper-church-2-injured
Former NTSB Expert Finds Explanation For Ground Stop “Baffling”
Gregory Feith Said Having One Router As A Single Point Of Failure Does Not Make Sense
Days after the FAA ordered a nationwide ground stop, the focus is shifting to what caused the disruption.
Transportation Secretary Sean Duffy won't apologize for the disruption. Instead, Sunday on Meet the Press, Duffy blamed prior administrations for "30 years" of a lack of investment. 
With flights running more smoothly on Monday, the question everyone wants answered is why did the disruption happen.
"Our switches, our routers actually got overloaded with data," Duffy said of the issue. "They started to give us inconsistency in the data, from those, from those routers. And because of that, we shut the system down." Duffy said a contractor was replacing a copper line with a fiber line which led a router to overwhelm the national FAA telecommunications network.
"Having one router as a single point failure just is baffling to me, and I think a lot of other people in aviation only because we certify aircraft never to have a single point failure,” said Feith, a veteran former Senior Air Safety Investigator and “Go-Team” captain with the National Transportation Safety Board. “So why is the air traffic control system vulnerable to a single point failure? That doesn't make any sense," he told 9NEWS in Denver.
Feith said work to modernize the system, switching from copper wire to fiber, has been happening long before the Trump administration, despite Duffy's claims.
"They've changed out 70% of the old copper wire to fiber. That's been ongoing well before the Trump administration. And in fact, modernization of the air traffic control system really started in 2003," Feith said.
And, Feith said, it doesn't explain the issue that created so many problems for the FAA.
"A router doesn't care if it's talking on a copper wire or a fiber optic cable. The fact is, is, yes, it may be old, and yes, that, that equipment needs to be upgraded, but the system, with the current old technology has been working just fine, and it worked just fine up until about 3:44 on Friday afternoon," Feith said.
File photo Gregory Feith Wikimedia Commons
FMI: www.faa.gov
NTSB Prelim: Cessna 182N
As The Pilot Applied Brakes To Slow The Airplane To Exit Onto A Taxiway And The Nose Of The Airplane Impacted The Runway
Location: Santa Maria, CA Accident Number: WPR27LA026
Date & Time: October 28, 2026, 12:10 Local Registration: N442RA
Aircraft: Cessna 182N Injuries: 2 None
Flight Conducted Under: Part 91: General aviation - Personal
On October 28, 2026, about 1210 Pacific daylight time, a Cessna 182N, N442RA was substantially damaged when it was involved in an accident near Santa Maria, California. The pilot and passenger were not injured.
The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. According to the pilot, the flight originated at Santa Maria Public Airport/Capt G Allen Hancock Field (SMX), Santa Maria, California, with several touch and go landings before the airplane departed the airport traffic pattern for a local flight.
The airplane returned to SMX for landing and the pilot did not observe any indication of a landing gear malfunction during touch down or the initial landing roll on runway 30. As the pilot applied brakes to slow the airplane to exit onto a taxiway and the nose of the airplane impacted the runway.
Postaccident examination of the airplane revealed that the fuselage was substantially damaged, and the nose landing gear had collapsed. The wreckage was retained for further examination.
FMI: www.ntsb.gov

Today in History
13 Years ago today: On 17 November 2013 Tatarstan Airlines flight 363, a Boeing 737-500, crashed following a loss of control while on approach to Kazan Airport, Russia, killing all 50 occupants.
| Date: | Sunday 17 November 2013 |
| Time: | 19:23 |
| Type: | Boeing 737-53A |
| Owner/operator: | Tatarstan Airlines |
| Registration: | VQ-BBN |
| MSN: | 24785/1882 |
| Year of manufacture: | 1990 |
| Total airframe hrs: | 51547 hours |
| Cycles: | 36596 flights |
| Engine model: | CFMI CFM56-3C1 |
| Fatalities: | Fatalities: 50 / Occupants: 50 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Kazan International Airport (KZN) - Russia |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Moskva-Domodedovo Airport (DME/UUDD) |
| Destination airport: | Kazan International Airport (KZN/UWKD) |
| Investigating agency: | MAK |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
Tatarstan Airlines flight 363, a Boeing 737-500, crashed following a loss of control while on approach to Kazan Airport, Russia, killing all 50 occupants.
Flight 363 departed from Moscow's Domodedovo Airport (DME) at 18:20 local time on a scheduled service to Kazan (KZN).
En route the crew noted that their navigation system's map was displaced. During the descent towards Kazan did not ask for vectors from air traffic control and continued their approach, which was flown 4 km to the north of the published approach procedure due to the map displacement issue.
After turning to final for runway 29 the aircraft was not able to capture the localizer. The flight crew programmed a heading of 250° in the HDG SEL (Heading Select mode) of the autopilot and hurriedly configured the aircraft for landing. The approach was unstabilized and as the aircraft turned towards runway heading the copilot noticed the PAPI lights and saw they were too high. He initiated a go around. At that time the aircraft was at 270m (900 ft) and configured for landing with gear down, 30° flaps. The autopilot was in ALT HOLD mode with altitude programmed at 270 m.
The use of the TO/GA switch caused the autopilot to be switched off. The flaps were raised to 15°, but no manual control inputs were made. The increase in engine power and retracting the flaps caused a pitch-up of the airplane with the pitch angle reaching a value of about to 25°. Indicated airspeed began to decrease, the stabilizer automatically trimmed nose down.
All the time the copilot was engaged in radio communications with the Kazan Tower controller. Subsequently the copilot reminded the captain to raise the undercarriage.
With the pitch angle exceeding 25° the crew began using the control column to reduce the pitch angle. At this point, the aircraft was at an altitude of about 600 meters (2,000 feet), and continued to climb with a vertical speed of 20 m/s. Due to nose down input by the captain and trim system, the pitch angle decreased quickly. Vertical loads decreased to 0,5 g as the aircraft had reached the top of climbing at 2300 feet / 700 meters. Indicated airspeed had decreased to its minimum value of 117 knots.
Vertical loads then decreased to about 0 g, with a negative pitch angle reaching 20°. The aircraft descended at a rate of more than 5000 ft/min (25 m/s).
The EGPWS gave "sink rate" and "pull up" warnings as the aircraft pitch angle reached -60° with a load of -0.9 g.
The aircraft collided with the ground at high speed, over 450 km/h, and a large negative pitch angle of about 75°. From the beginning of the missed approach until the collision with terrain, 45 seconds passed.
The aircraft impacted the ground between the runway and the main taxiway about 1850 m past the runway 29 threshold.
Investigation revealed that the captain received training to become a Boeing 737 captain after serving as a navigator between 1991 and 2010. The copilot used to be a flight engineer (1989 to 2008) and was also trained to become a Boeing 737 pilot. The captain had a very limited knowledge of English, which was considered insufficient to comprehend English language training documents and manuals. As the oversight of the training facility was poor, shortcomings in training were not noticed. Training and safety management within Tatarstan Airlines was considered equally poor.
PROBABLE CAUSE (translated from Russian):
The cause of the crash Boeing 737-500 VQ-BBN were systemic deficiencies in the identification of hazards and risk control, as well as a non-functional safety management system in the airline and the lack of control over the level of training of the crew members from the aviation authorities at all levels (Tatar MTU BT, Federal Air Transport Agency), which led to the admission of an unprepared flight crew.
When the missed approach was executed the crew did not recognize the fact that the autopilot was off and the aircraft pitched up to a complex spatial position (Nose up Upset). The PIC's (pilot flying) lack of flying skills in complex spatial positions (Upset Recovery) led to the creation of a large negative overload, loss of spatial orientation and transfer of the aircraft into a steep dive (pitch down to 75°) until the impact with the ground.
The need for a go-around was caused by the position of the aircraft relative to the runway, which was the result of "a map shift" effect (Map shift, an error in the determination of the aircraft position by onboard systems) by about 4 km, the crew's inability in the circumstances to integrated piloting and maintenance of navigation with the required accuracy, and the lack of active assistance of the air traffic control service under the long-term monitoring of significant deviations from the approach procedure.
METAR:
14:30 UTC / local time:
UWKD 171430Z 23009G12MPS 9999 OVC009 03/02 Q0995 R29/2/0055 NOSIG RMK QFE735/0980
15:00 UTC / local time:
UWKD 171500Z 23009G12MPS 9999 -RASN OVC008 03/02 Q0994 R29/2/0055 NOSIG RMK QFE735/0980
Wind 230 degrees at 9m/s, gusting to 12 m/s; light rain, light snow; Overcast at 800 feet; Temperature: 3°C, Dewpoint: 2°C; Pressure: 994 mb
15:30 UTC / local time:
UWKD 171530Z 23008G11MPS 5000 -RASN OVC007 03/03 Q0993 R29/2/0055 NOSIG RMK QFE734/0979
Wind 230 degrees at 8 m/s, gusting to 11 m/s; visibility 5000 m; light rain, light snow; Overcast at 700 feet; Temperature: 3°C, Dewpoint: 3°C; Pressure: 993 mb
ICAO Occurrence Category:
LOC-I: Loss of Control–Inflight
