November 11th is Veterans Day, the day that
honors ALL American veterans, both living and dead.
It also coincides with other holidays including Armistice Day and Remembrance Day which are celebrated in other countries that mark the anniversary of the end of World War I.
Major hostilities of World War I were formally
ended at the 11th hour of the 11th day of the 11th month of 1918, when the Armistice with Germany went into effect.
At the urging of major U.S. veteran organizations, Armistice Day was renamed Veterans Day in 1954.
Veterans Day is largely intended to thank LIVING veterans for dedicated and loyal service to their country. November 11 of each year is the day that we ensure veterans know that we deeply appreciate the sacrifices they have made in their lives to keep our country free.
I ask all of you to remember these words spoken by Abraham Lincoln; “Honor to the soldier and sailor everywhere, who bravely bears his country’s cause. Honor, also, to the citizen who cares for his brother in the field and serves, as he best can, the same cause.”
To all of my friends who have served in our nation’s military, Thank You!
And I would be remiss if I did not point out
that yesterday was the birthday of the United States Marine Corps. The United States Marine Corps birthday is celebrated every year on the 10th of November with a traditional ball and cake-cutting ceremony as it was on this day in 1775, the Continental Marines were established.
Happy Birthday Marines!
Now here are the stories for today…
Be safe out there!
Tom
-
Airport Transporter Crashes at Dulles, Causing Injuries and Damage
More than a dozen people were hospitalized after a bus-like vehicle for passengers crashed into a dock at the Washington airport.
By Alexandra E. Petri
A mobile lounge carrying passengers crashed at
Washington Dulles International Airport on Monday, injuring more than a dozen people and causing some damage to the terminal.
At around 4:30 p.m. Monday, a mobile lounge transporting passengers from Concourse D struck a dock at an angle as it was pulling up to the terminal, Crystal L. Nosal, a spokeswoman for the Metropolitan Washington Airports Authority, said in a statement. She added that the airport was open and operating as normal Monday evening.
Passengers exited the mobile lounge using the stairs, and 18 people were taken to a hospital with injuries that were not life-threatening, Ms. Nosal said.
According to the airport’s website, Dulles has a fleet of 19 mobile lounges, which transport passengers between the terminal and Concourses A and D. One mobile lounge can carry 102 passengers. They were first introduced in 1959, when Dulles airport was under construction, as the system that would transport passengers around the airport. An article by The New York Times described the mobile lounge as “a bus, but not exactly.”
Air travel has been disrupted across the country in recent days, after the Trump administration announced that up to 10 percent of flights at 40 U.S. airports, including Dulles, would be cut because of the government shutdown. Thousands of flights have been canceled and delays have piled up, frustrating travelers.
In his Senate confirmation hearing this week for his nomination to the board of the Metropolitan Washington Airports Authority, Trent Morse, a former White House staff member, said “the people mover is a relic of the past.”
“It’s an embarrassment that international travelers when visiting the capital of the most powerful nation in the world are transported back to the ’60s,” Mr. Morse said.
The mobile lounges have come under fire in the past.
A 2017 investigation by NBC4 Washington found that the mobile lounges, also called people movers, had been involved in at least 16 collisions or mishaps since 2007, including one fatal accident and others that caused injuries.
https://www.nytimes.com/2025/11/10/us/dulles-airport-crash-mobile-lounge.html
Plane bound for Jamaica to aid in hurricane relief crashes into South Florida backyard
by Grace Bellinghausen
CORAL SPRINGS, Fla. (CBS12) — A small plane
headed to Jamaica to aid in hurricane relief efforts crashed into a Coral Springs neighborhood on Monday.
The crash happened at 10:20 a.m. in the 5700 block of NW 57th, according to the Coral Springs Police Department.
Aerial footage shows the impact damaged a fence and trees in the backyard of a residence before it plummeted into a man-made pond.
A spokesperson with Fort Lauderdale Executive Airport told CBS Miami that the Beechcraft King Air twin-turboprop plane took off at 10:14 en route to Jamaica to aid in relief efforts in the wake of Hurricane Melissa.
Crews closed Creekside Drive between NW 53rd Drive to clear the scene, per reports. Coral Springs Police ask residents who locate debris to call the department at 954-344-1800.
Authorities have not released the condition of the plane's occupants at this time. The investigation is ongoing.
https://cbs12.com/news/local/plane-bound-for-jamaica-crashes-into-south-florida-backyard-fort-lauderdale-executive-airport-beechcraft-king-coral-springs-police-november-10-2025
Small plane crashes in Castle Rock, temporarily shutting down traffic north of Cedar Hill Cemetery
By: Óscar Contreras
CASTLE ROCK, Colo. — A small plane crash north
of Cedar Hill Cemetery temporarily shut down traffic in Castle Rock Monday evening, according to officers with the Castle Rock Police Department.
No one was injured in the crash and there were no additional hazards in the area after the aircraft, which appeared to be a Piper fixed wing, single-engine plane, crashed just before 6:15 p.m. near the intersection of Wolfensberger Road and Prairie Hawk Drive.
The aircraft was towed, and the roads were reopened by 8:30 p.m.
Castle Rock Fire Chief Norris Croom told Denver7 the plane had three passengers and took off from Centennial Airport.
According to the pilot, Croom said, the plane lost power after takeoff and the pilot realized he could not make it back to Centennial. The pilot then saw a mostly clear street and landed the plane on Prairie Hawk Drive.
Croom said the plane hit the back of a car on the street, causing some damage. But the two car passengers did not need medical attention and were able to drive away from the scene, Croom said.
The plane crash landed between a residential neighborhood on one side of the street and a power station on the other.
"Normally what we see out of the movies... is a much worse situation," Croom said. "And tonight, we're very fortunate."
The Federal Aviation Administration (FAA) and the National Transportation Safety Board (NTSB) were notified of the crash and were expected to investigate the circumstances that lead to the downed plane in the coming days.
https://www.denver7.com/news/front-range/castle-rock/small-plane-crashes-in-castle-rock-temporarily-shutting-down-traffic-north-of-cedar-hill-cemetery
NTSB Prelim: Socata TBM 700
The Controller Provided The Pilot With A Low Altitude Alert And The Altimeter Setting That Was Current At The Time
Location: Dartmouth, MA Accident Number: ERA26FA011
Date & Time: October 13, 2025, 08:15 Local Registration: N111RF
Aircraft: Socata TBM 700 Injuries: 2 Fatal, 1 Minor
Flight Conducted Under: Part 91: General aviation - Personal
On October 13, 2025, at about 0815 eastern daylight time, a Socata TBM 700C2, N111RF, was substantially damaged when it was involved in an accident near Dartmouth, Massachusetts. The private pilot and the passenger were fatally injured and an automobile driver received minor injuries. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight.
According to preliminary air traffic control ADS-B and voice communication data provided by the Federal Aviation Administration, the pilot had filed an instrument flight rules flight plan from New Bedford Regional Airport (EWB), New Bedford, Massachusetts, to the Kenosha Regional Airport (ENW), Kenosha, Wisconsin. The airplane departed EWB at 0805, and shortly after departure, the pilot stated that he would be returning to the airport. The air traffic controller then instructed the pilot to enter a left downwind for runway 05, an instruction which the pilot confirmed. The controller then queried the pilot if he would need assistance upon landing, to which the pilot reported that he did not need assistance. The controller then cleared the pilot to land on runway 05.
The controller next asked the pilot whether he could perform an approach to the airport and reported that the ceilings were around 1,000 ft, or if he would need radar vectors. The pilot responded that he would descend and that he “should be OK.” The controller acknowledged the pilot and cleared him again to land on runway 05. About one minute later, the controller provided the pilot with a low altitude alert and the altimeter setting that was current at the time. The pilot confirmed the altimeter setting. Shortly after, the pilot made an unintelligible exclamation. There were no further communications from the pilot.
The accident site was located about 3.6 nautical miles southwest of EWB. Several trees that were impact-damaged were identified as the initial impact points. The trees had the tops cut off approximately 50 feet above the ground. The wreckage path continued through a wooded area, across a highway off ramp, across a portion of Interstate 195 West, and the fuselage came to rest in the median between Interstate 195 West and Interstate 195 East. During the impact sequence, the airplane impacted an automobile that was traveling on Interstate 195 West and the driver received minor injuries. The distance from the initial impact point to where the fuselage came to rest was about 280 ft. The debris path was oriented along a heading of 223° true, and the fuselage came to rest oriented on a heading of 289° true. A post-impact fire consumed portions of both wings and the empennage. All of the major components of the airplane were located at the accident site.
Both wings were impact damaged, and portions of both wings had been partially consumed by a post-impact fire. The left aileron was located along the wreckage path and the aileron trim tab remained attached. The rudder sustained significant impact damage to the leading edge, and a portion of the rudder had broken free from the rest of the rudder. The rudder trim tab remained attached to the rudder through its hinge; however, the rudder trim actuator had separated from the rudder trim tab; the damage was consistent with impact. The elevator trim tab remained partially attached to the elevator through the trim tab actuator and the trim tab and both elevators were impact and thermally-damaged.
The wing fuel tanks were breached, and no fuel was recovered from the remnants of the fuel tanks; however, there was a strong odor consistent with Jet A fuel noted around the accident site. The fuel strainer bowl and screen remained secured, and there were no signs of fuel leaks. The bowl was removed, and the screen was clear of obstructions. The fuel contamination indicator was in its normal position. The fuel line connecting the fuel outlet at the firewall to the fuel pump inlet was secure and there were no signs of fuel leaks. The fuselage was the furthest piece of wreckage observed along the wreckage path and remained mostly intact; however, the fuselage structure was buckled in multiple locations, and there was a small portion of thermal damage to the forward left side of the fuselage. A portion of the left wing root remained attached to the fuselage, the right wing had completely impact separated from the fuselage. The main cabin door was found open when the investigators arrived; however, a witness video that was taken after the accident showed that the cabin door was closed immediately after the accident. Both forward seats had impact-separated from their installation points and remained within the cabin area.
The airplane was equipped with a digital avionics suite. Both the pilot and copilot primary flight displays (PFD) remained installed, and the electrical connectors remained secured. Both flight displays were recovered and retained for data download.
The engine remained partially attached to the airframe through the engine mounts, cables, wires, and hoses. The engine displayed some impact damage signatures and there were no signs of fire. The five blade, constant speed, composite propeller sustained impact damage to all five blades. The propeller blade hub remained attached to the propeller flange. All five of the propeller blades had separated from the propeller hub near their roots, and all of the propeller blades were located along the wreckage path. The blades displayed varying amounts of leading-edge damage.
The wreckage was retained for further examination.
FMI: www.ntsb.gov

Today in History
60 Years ago today: On 11 November 1965 United Airlines flight 227, a Boeing 727, crashed while on approach to Salt Lake City Airport, Utah, USA, killing 43 occupants; 48 survived the accident.
| Date: | Thursday 11 November 1965 |
| Time: | 17:52 |
| Type: | Boeing 727-22 |
| Owner/operator: | United Airlines |
| Registration: | N7030U |
| MSN: | 18322/130 |
| Year of manufacture: | 1965 |
| Total airframe hrs: | 1781 hours |
| Engine model: | P&W JT8D-1 |
| Fatalities: | Fatalities: 43 / Occupants: 91 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Salt Lake City International Airport, UT (SLC) - United States of America |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Denver-Stapleton International Airport, CO (DEN/KDEN) |
| Destination airport: | Salt Lake City International Airport, UT (SLC/KSLC) |
| Investigating agency: | CAB |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
United Airlines flight 227, a Boeing 727, crashed while on approach to Salt Lake City Airport, Utah, USA, killing 43 occupants; 48 survived the accident.
Flight UA227 took off from New York-LaGuardia (LGA) for a flight to San Francisco (SFO) via Cleveland (CLE), Chicago (MDW), Denver (DEN) and Salt Lake City (SLC). The aircraft took off from Denver at 16:54 and climbed to its assigned cruising altitude of FL310. At 17:38 flight 227 began its descent for Salt Lake City. The flight proceeded in accordance with radar vectors. After a radar handoff to Salt Lake City Approach Control new clearance altitudes were given. At 17:47 the approach controller advised, "United seventy twenty seven ... five miles south of Riverton Fan Marker coming on localizer course cleared for ILS runway three four left approach." The pilot replied "Okay we're slowed to two fifty (Knots) and we're at ten (10,000 feet) we have the runway in sight now, we'll cancel and standby with you for traffic." Control of the flight was transferred to the tower and at 17:49:40 landing clearance was issued.
The aircraft crossed the outer marker over 2,000 feet above the ILS glide slope. The rate of descent during the final approach exceeded 2,000 ft/min, approximately three times the United Air Lines recommended rate of descent for landing approaches. The first officer attempted to apply power but the captain stopped him. Power was then applied too late to arrest the rate of descent. The airplane touched down 335 feet short of the threshold of runway 34L. The right and left main landing gear began to separate and the airplane slid onto the runway. Severe upward and rearward impact forces from the right main Landing gear assembly produced a large impact hole and ruptured fuel lines and the no. 3 generator leads between fuselage station 1030 and 1130 on the right side. The fuel was ignited by sparks from the fuselage scraping on the runway and/or the severed generator leads.
PROBABLE CAUSE: "The failure of the captain to take timely action to arrest an excessive descent rate during the landing approach."

honors ALL American veterans, both living and dead.
ended at the 11th hour of the 11th day of the 11th month of 1918, when the Armistice with Germany went into effect.
that yesterday was the birthday of the United States Marine Corps. The United States Marine Corps birthday is celebrated every year on the 10th of November with a traditional ball and cake-cutting ceremony as it was on this day in 1775, the Continental Marines were established.