Your stories for today...
Be safe out there!
Tom
--
Corporate Jet Collides With Box Truck at Raleigh-Durham Airport
Edited by: Rounak Bagchi
Two people were on board the aircraft and one person was driving the truck. Airport officials said no injuries were reported.
A corporate jet and a box truck collided on a taxiway at
North Carolina's Raleigh-Durham International Airport on Wednesday, prompting a temporary closure of the airfield, airport officials said. The collision occurred on Taxiway C and involved a general aviation aircraft and a box truck, according to Raleigh-Durham International Airport (RDU).
Two people were on board the aircraft and one person was driving the truck. Airport officials said no injuries were reported.
The airfield was briefly closed while the incident was investigated before reopening later on Wednesday. "The airfield is now open and operating normally for arriving and departing flights," RDU said in a statement.
The cause of the collision has not been determined and remains under investigation.
Airplane crashed in Lancaster County overnight, officials confirm
Plane crash happened near Brooklyn Avenue
By Luke Tucker
LANCASTER, S.C. (WBTV) - An airplane crashed in
Lancaster County early Thursday morning, officials confirmed.
The crash was reported around 1:45 a.m. on July 2, behind a metal recycling plant on Brooklyn Avenue.
A local fire official initially confirmed the crash before the Federal Aviation Administration (FAA) later said the plane was a Beechcraft BE55 and that two people were onboard.
A Lancaster County Sheriff’s Office spokesman said in a Thursday morning news conference that the plane’s pilot reported losing engine power before it crashed. During that same news conference, the spokesman said the two people onboard were taken to burn centers but were alive and responsive when first responders arrived.
FlightAware data showed that around the reported time, a Beechcraft airplane went down in the reported area. Flight records showed that plane took off from an airport in Mississippi and was en route to Stanly County, N.C. Records revealed the plane was registered to a flight school in Stanly County.
The area where the crash happened is just south of Lancaster, right outside city limits.
https://www.wbtv.com/2026/07/02/airplane-crashed-lancaster-county-overnight-officials-confirm/
NTSB Final Report: Danchini Aero Danchini Cub
Pilot Stated That Prior To Takeoff He Moved The Fuel Selector Valve From Left Fuel Tank To The Both Position
Location: Wasilla, Alaska Accident Number: ANC26LA007
Date & Time: November 24, 2025, 14:00 Local Registration: N794AK
Aircraft: Danchini Aero Danchini Cub Aircraft Damage: Substantial
Defining Event: Fuel starvation Injuries: 2 None
Flight Conducted Under: Part 91: General aviation - Personal
Analysis: The pilot stated that prior to takeoff he moved the fuel selector valve from left fuel tank to the both position. Shortly after takeoff the engine lost all power, unable to return to the runway the pilot performed a forced landing onto a road. The airplane sustained substantial damage to the wings.
After the accident, the pilot realized he mistook the fuel selector handle for the indicator and misinterpreted the position the fuel selector was in. He had actually turned the fuel to the off position prior to takeoff, not the both position as he believed he had. The pilot reported that there were no preaccident mechanical malfunctions or failures with the airplane that would have precluded normal operation.
Probable Cause and Findings: The National Transportation Safety Board determines the probable cause(s) of this accident to be -- The pilot’s inadequate preflight inspection, and inadequate inflight fuel management, which resulted in a total loss of engine power due to fuel starvation and subsequent forced landing.
FMI:Â www.ntsb.gov

Today in History
32 Years ago today:Â On 2 July 1994 USAir flight 1016, a DC-9-31, crashed following a windshear encounter while on approach to Charlotte-Douglas Airport, North Carolina, USA, killing 37 occupants; 20 survived the accident.
| Date: | Saturday 2 July 1994 |
| Time: | 18:43 |
| Type: | McDonnell Douglas DC-9-31 |
| Owner/operator: | USAir |
| Registration: | N954VJ |
| MSN: | 47590/703 |
| Year of manufacture: | 1973 |
| Total airframe hrs: | 53917 hours |
| Cycles: | 63147 flights |
| Engine model: | P&W JT8D-7B |
| Fatalities: | Fatalities: 37 / Occupants: 57 |
| Other fatalities: | 0 |
| Aircraft damage: | Destroyed, written off |
| Category: | Accident |
| Location: | Charlotte-Douglas Airport, NC (CLT) -Â Â Â Â United States of America |
| Phase: | Approach |
| Nature: | Passenger - Scheduled |
| Departure airport: | Columbia Metropolitan Airport, SC (CAE/KCAE) |
| Destination airport: | Charlotte-Douglas Airport, NC (CLT/KCLT) |
| Investigating agency:Â | NTSB |
| Confidence Rating: | Â Accident investigation report completed and information captured |
Narrative:
USAir flight 1016, a DC-9-31, crashed following a windshear encounter while on approach to Charlotte-Douglas Airport, North Carolina, USA, killing 37 occupants; 20 survived the accident.
USAir Flight 1016 was a domestic flight from Columbia (CAE) to Charlotte (CLT). The DC-9 departed the gate on schedule at 18:10. The first officer was performing the duties of the flying pilot. ![]()
The weather information provided to the flightcrew from USAir dispatch indicated that the conditions at Charlotte were similar to those encountered when the crew had departed there approximately one hour earlier. The only noted exception was the report of scattered thunderstorms in the area.
Flight 1016 was airborne at 18:23 for the planned 35 minute flight. At 18:27, the captain of flight 1016 made initial contact with the Charlotte Terminal Radar Approach Control (TRACON) controller and advised that the flight was at 12,000 feet mean sea level (msl). The controller replied "USAir ten sixteen ... expect runway one eight right." Shortly afterward the controller issued a clearance to the flightcrew to descend to 10,000 feet. At 18:29, the first officer commented "there's more rain than I thought there was ... it's startin ...pretty good a minute ago ... now it's held up." On their airborne weather radar the crew observed two cells, one located south and the second located east of the airport. The captain said "looks like that's [rain] setting just off the edge of the airport." One minute later, the captain contacted the controller and said "We're showing uh little buildup here it uh looks like it's sitting on the radial, we'd like to go about five degrees to the left to the ..." The controller replied "How far ahead are you looking ten sixteen?" The captain responded "About fifteen miles." The controller then replied "I'm going to turn you before you get there I'm going to turn you at about five miles northbound." The captain acknowledged the transmission, and, at 18:33, the controller directed the crew to turn the aircraft to a heading of three six zero. One minute later the flightcrew was issued a clearance to descend to 6,000 feet, and shortly thereafter contacted the Final Radar West controller.
At 18:35 the Final Radar West controller transmitted "USAir ten sixteen ... maintain four thousand runway one eight right.'' The captain acknowledged the radio transmission and then stated to the first officer "approach brief." The first officer responded "visual back up ILS." Following the first officer's response, the controller issued a clearance to flight 1016 to "...turn ten degrees right descend and maintain two thousand three hundred vectors visual approach runway one eight right.''
At 18:36, the Final Radar West controller radioed flight 1016 and said "I'll tell you what USAir ten sixteen they got some rain just south of the field might be a little bit coming off north just expect the ILS now amend your altitude maintain three thousand." At 18:37, the controller instructed flight 1016 to ''turn right heading zero niner zero." At 18:38, the controller said "USAir ten sixteen turn right heading one seven zero four from SOPHE [the outer marker for runway 18R ILS] ... cross SOPHE at or above three thousand cleared ILS one eight right approach." As they were maneuvering the airplane from the base leg of the visual approach to final, both crew members had visual contact with the airport. The captain then contacted Charlotte Tower. The controller said "USAir ten sixteen ... runway one eight right cleared to land following an F-K one hundred short final, previous arrival reported a smooth ride all the way down the final." The pilot of the Fokker 100 in front also reported a "smooth ride". About 18:36, a special weather observation was recorded, which included: ... measured [cloud] ceiling 4,500 feet broken, visibility 6 miles, thunderstorm, light rainshower, haze, the temperature was 88 degrees Fahrenheit, the dewpoint was 67 degrees Fahrenheit, the wind was from 110 degrees at 16 knots .... This information was not broadcast until 1843; thus, the crew of flight 1016 did not receive the new ATIS.
At 18:40, the Tower controller said "USAir ten sixteen the wind is showing one zero zero at one nine." This was followed a short time later by the controller saying "USAir ten sixteen wind now one one zero at two one." Then the Tower controller radioed a wind shear warning "windshear alert northeast boundary wind one nine zero at one three.''
On finals the DC-9 entered an area of rainfall and at 18:41:58, the first officer commented "there's, ooh, ten knots right there." This was followed by the captain saying "OK, you're plus twenty [knots] ... take it around, go to the right." A go around was initiated. The Tower controller noticed Flight 1016 going around "USAir ten sixteen understand you're on the go sir, fly runway heading, climb and maintain three thousand."
The first officer initially rotated the airplane to the proper 15 degrees nose-up attitude during the missed approach. However, the thrust was set below the standard go-around EPR limit of 1.93, and the pitch attitude was reduced to 5 degrees nose down before the flightcrew recognized the dangerous situation. When the flaps were in transition from 40 to 15 degrees (about a 12-second cycle), the airplane encountered windshear. Although the DC-9 was equipped with an on-board windshear warning system, it did not activate for unknown reasons. The airplane stalled and impacted the ground at 18:42:35.
Investigation revealed that the headwind encountered by flight 1016 during the approach between 18:40:40 and 18:42:00 was between 10 and 20 knots. The initial wind component, a headwind, increased from approximately 30 knots at 18:42:00 to 35 knots at 18:42:15. The maximum calculated headwind occurred at 18:42:17, and was calculated at about 39 knots. The airplane struck the ground after transitioning from a headwind of approximately 35 knots, at 18:42:21, to a tailwind of 26 knots (a change of 61 knots), over a 14 second period.
PROBABLE CAUSE: "1) the flight crew's decision to continue an approach into severe convective activity that was conducive to a microburst; 2) the flight crew's failure to recognize a windshear situation in a timely manner; 3) the flight crew's failure to establish and maintain the proper airplane attitude and thrust setting necessary to escape the windshear; and 4) the lack of real-time adverse weather and windshear hazard information dissemination from air traffic control, all of which led to an encounter with and failure to escape from a microburst-induced windshear that was produced by a rapidly developing thunderstorm located at the approach end of runway 18R.
Contributing to the accident were: 1) the lack of air traffic control procedures that would have required the controller to display and issue ASR-9 radar weather information to the pilots of flight 1016; 2) the Charlotte tower supervisor's failure to properly advise and ensure that all controllers were aware of and reporting the reduction in visibility and the RVR value information, and the low level windshear alerts that had occurred in multiple quadrants; 3) the inadequate remedial actions by USAir to ensure adherence to standard operating procedures; and 4) the inadequate software logic in the airplane's windshear warning system that did not provide an alert upon entry into the windshear."
