Here are your stories for today...
Be safe out there!
Tom
--
Small plane lands on rural Nebraska road after engine failure, no injuries reported
By 10/11 NOW
RICHARDSON COUNTY, Neb. (KOLN) - A plane made a safe emergency landing on a road in Richardson County after experiencing engine issues Sunday night. 
According to the FAA’s Aviation Safety Information Analysis and Sharing, the emergency happened around 8:07 p.m. near the intersection of 652 Avenue and 714 Road.
Deputies, along with Falls City Rural Fire and Falls City EMS, responded to the scene. Upon arrival, emergency responders found a single-engine Cessna aircraft that had successfully completed an emergency landing following an apparent engine failure.
Two people on board were not injured.
The aircraft was moved off the county road and onto private property near the landing site so the roadway could be reopened. The sheriff’s office said it remains at that location pending recovery and investigation by the appropriate federal aviation authorities.
The National Transportation Safety Board, in coordination with the FAA, will investigate the cause of the emergency landing.
No injuries reported in Pine River airplane crash
By Pineandlakes Echo Journal
PINE RIVER — No injuries were reported when an airplane carrying six people had an issue with landing gear Sunday, July 5, at the Pine River Regional Airport. 
Cass County Sheriff Bryan Welk said in a news release that at 2:58 p.m. Sunday, the Cass County Sheriff’s Office received reports of a plane crash on the runway at the Pine River airport.
Responders arrived and learned that a 1984 Beechcraft Bonanza was landing when an issue was discovered with the landing gear. The plane landed and skidded along the runway for a distance until coming to a stop.
The plane was piloted by a 71-year-old man from Pella, Iowa, and had five passengers, including three juveniles.
The plane was removed from the runway and debris was cleaned up. The airport was closed for a short period of time and the incident remains under investigation with the assistance of the Pine River Police Department, the Federal Aviation Administration and the National Transportation Safety Board.
https://www.pineandlakes.com/news/local/no-injuries-reported-in-pine-river-airplane-crash
NTSB Prelim: Lancair 235
(Witness) Reported The Airplane’s Nosewheel Lifted Off The Runway Surface Within The First Third Of The Runway And Subsequently Settled Back To The Runway
Location: Hillsboro, OR Accident Number: WPR26FA217
Date & Time: June 12, 2026, 15:08 Local Registration: N10CF
Aircraft: Lancair 235 Injuries: 1 Fatal
Flight Conducted Under: Part 91: General aviation - Personal
On June 12, 2026, at about 1508 Pacific daylight time, a Lancair 235, N10CF, was destroyed when it was involved in an accident near Hillsboro, Oregon. The pilot was fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. A pilot-rated witness located near the runway, just south of midfield, observed the accident sequence. During the airplane’s takeoff roll on runway 02, he reported the airplane’s nosewheel lifted off the runway surface within the first third of the runway and subsequently settled back to the runway. He observed the nosewheel rise off the runway a second time, followed by a reduction of engine noise. He also noted that the airplane appeared to decelerate. As the airplane crossed about the runway midpoint, he heard the engine noise increase. He lost sight of the airplane as it passed behind a rise in the terrain. He then heard sounds that he associated with the airplane impacting terrain.
A second pilot-rated witness stated he observed the airplane start its takeoff roll and observed the nose lift off about halfway down the runway, though the airplane was not yet airborne. The airplane briefly passed behind a building, obscuring his view, at which time he heard a reduction in engine noise. He then heard a sound he associated with heavy braking, followed by the application of engine power. About two seconds later, he heard a second reduction in power and a sound of “locked up brakes.” The airplane came back into his field of view, and he observed white smoke from the tires.
Another witness, who was located about 500 ft northeast of the departure end of runway 02, stated that he heard tires “chirping” followed by the sound of an engine “rev.” He then saw an airplane come off the end of the runway at a low altitude. He stated that the nose of the airplane pitched up and then the airplane rolled left. He observed the left wing impact terrain and the airplane cart-wheel before coming to rest and catching fire.
Dashcam footage obtained from the driver of a privately owned vehicle traveling eastbound on SW River Road depicted the accident airplane exiting the departure end of runway 02 in a nosehigh attitude. The camera’s view of the airplane was temporarily obstructed by vegetation; it then reappeared in a left-bank attitude as the left wing impacted terrain.
Examination of the runway surface revealed parallel, dark skid marks consistent with the accident airplane’s main landing gear tire tread and track width. The skid marks began about 1,000 ft from the start of runway 02, beginning with an intermittent mark from the right tire about 90 ft long, then continuing with marks from both tires for about 160 additional feet. A second set of skid marks was identified, beginning about 1,800 ft from the start of runway 02 and continuing for about 660 ft. A 66-inch-long gouge was observed in the pavement, extending off the departure end of runway 02. The gouge contained abraded material consistent with composite rudder material from the accident airplane.
The wreckage was located in an area of uneven terrain in tall vegetation. All major structures were accounted for at the accident site. The airplane came to rest about 350 feet north of the runway on a magnetic heading of 195°. The first identified point of contact was disturbed soil located about 33 feet south of the main wreckage, where a single propeller blade was embedded. The fuselage and cabin area were mostly consumed by fire. The left wing was also consumed by fire. The right wing was thermally damaged and mostly intact, and the right-wing fuel tank was thermally damaged and breached. The empennage was separated from the fuselage and located adjacent to and north of the main wreckage; it sustained thermal damage, but was largely intact. The engine and firewall structure were thermally damaged, separated from the fuselage and located alongside and north of the main wreckage. The lower edge of the rudder exhibited abraded material consistent with the pavement gouge observed at the departure end of runway 02.
The wreckage was retained for further examination.
FMI: www.ntsb.gov

Today in History
64 Years ago today: On 7 July 1962 Alitalia flight AZ771, a Douglas DC-8-43, impacted a mountain near Junnar, India, killing all 94 occupants.
| Date: | Saturday 7 July 1962 |
| Time: | 00:10 |
| Type: | Douglas DC-8-43 |
| Owner/operator: | Alitalia |
| Registration: | I-DIWD |
| MSN: | 45631/160 |
| Year of manufacture: | 1962 |
| Total airframe hrs: | 964 hours |
| Engine model: | Rolls-Royce Conway 508-12 |
| Fatalities: | Fatalities: 94 / Occupants: 94 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | 11 km NW of Junnar - India |
| Phase: | En route |
| Nature: | Passenger - Scheduled |
| Departure airport: | Bangkok-Don Muang International Airport (BKK/VTBD) |
| Destination airport: | Bombay-Santacruz Airport (BOM/VABB) |
| Confidence Rating: | Accident investigation report completed and information captured |
Narrative:
Alitalia flight AZ771, a Douglas DC-8-43, impacted a mountain near Junnar, India, killing all 94 occupants.
Alitalia flight 771 was a scheduled flight from Sydney (Australia) to Rome (Italy) via Darwin (Australia), Singapore, Bangkok (Thailand), Bombay (India), Karachi (Pakistan) and Tehran (Iran). It departed Bangkok Airport for Bombay-Santacruz Airport at 15:16 UTC (22:16 local time). At 18:20 UTC (22:50 local time) the crew contacted Bombay Approach and received clearance to descend from FL350 to FL200. Five minutes later further clearance was given to 4000 feet. In preparation for a runway 27 approach, the crew reported that they would make a 360 degrees turn over the Outer Marker. Last radio contact was at 18:39 (00:09 local time). The DC-8 had descended below minimum safe altitude and struck the Davandyachi Hill at an elevation of approximately 3600 ft amsl (1098 m).
PROBABLE CAUSE: "The accident was attributed to a navigation error which led the pilot to believe that he was nearer his destination than he actually was and, therefore, caused him to make a premature descent in instrument conditions for a straight-in approach to land at night. The aircraft consequently, crashed into high terrain. Contributing causes were: 1) Failure on the part of the pilot to make use of the navigational facilities available in order to ascertain the correct position of the aircraft.
2) Infringement of the prescribed minimum safe altitude. 3) Unfamiliarity of the pilot with the terrain on the route."
