GA mid air collision in CO
#21

Accidental Discharge became Negligent Discharge. Except in the very exceptionally rare cases where a modern weapon actually suffers a mechanical failure, but even that is likely to be somebody's fault, just maybe not the operator's.

#22

Karen wasn't doing 45 in a 25 in a SUV, while drinking a grande triple frapp with one hand, applying makeup with the other, and steering with her knee.
Not one but two kids just got creamed at the crosswalk at my kid's school. On Monday of this week.
Actually my kid did crosswalk guard in middle school, but they use stop signs on long poles so they didn't have to use their bodies to try to get karen to slow down.
Not one but two kids just got creamed at the crosswalk at my kid's school. On Monday of this week.
Actually my kid did crosswalk guard in middle school, but they use stop signs on long poles so they didn't have to use their bodies to try to get karen to slow down.
In fact, most of those mothers drove three on the tree standard transmission. I know my mom rode the clutch and had a firm grip with two hands on that steering wheel.
#23
Gets Weekends Off
Joined APC: Mar 2017
Posts: 128

The comments are interesting...
https://www.avweb.com/aviation-news/...ds-b-out-data/
Contrary to previous reports, the Sonex Xenos involved in the Sept. 17, 2022, triple-fatal midair collision in Colorado was not transmitting ADS-B “out” data at the time of the accident, according to the NTSB. ADS-B “out” is required within the Denver Mode C veil where the accident occurred. And the NTSB Preliminary Report (download PDF here) further states the aircraft’s last flight during which it broadcast ADS-B data was flown on July 14, a flight lasting six minutes, according to FlightAware.
Between that date and the accident date, FlightAware (which gets its data from numerous sources, including air traffic control and ADS-B) recorded eight more flights originating from the Sonex’s home airport (Platte Valley Airpark—18V), which lies well within the Mode C veil. The flights ranged in duration from 12 minutes to just less than an hour.
Both aircraft involved in the accident, the Sonex and a Cessna 172 Skyhawk on a training flight with two on board, were squawking VFR (1200) transponder codes. According to the text of the NTSB report, “Both airplanes operated within the Mode-C veil of the Denver International Airport Class B airspace that required automatic dependent surveillance broadcast (ADS-B) ‘out’ transmissions. The Cessna was equipped with ADS-B ‘in/out’ equipment and transmitted ADS-B data during the accident flight. The Sonex did not transmit ADS-B data during the accident flight …” Neither aircraft was in radio contact with ATC, nor were they required to be.
From the report: “A review of air traffic control (ATC) flight track data revealed the Cessna departed Rocky Mountain Municipal Airport (BJC), Denver, Colorado, about 0843, and the Sonex departed Platte Valley Airpark (18V), Hudson, Colorado, about 0838. The airplanes climbed to about 7,000-7,500 feet mean sea level (msl) [approximately 2,000 feet above ground level] and were operating under visual flight rules (VFR). The Cessna flew northbound and the Sonex flew westbound toward the Longmont area. After the Cessna completed a left 360-degree turn, it turned eastbound. The flight track data of the two airplanes merged and subsequently showed both airplanes rapidly descending.”
The FAA-registered owner of the Sonex, Henry Butler Jr., was the pilot on the accident flight and the sole occupant. According to FAA records, the aircraft was registered on Feb. 24, 2022. The previously listed owner was a limited liability corporation in Wisconsin. The corporation was listed as the registered owner from August 2016 until October 2021 when the aircraft was listed as “Registration Pending.”
https://www.avweb.com/aviation-news/...ds-b-out-data/
Contrary to previous reports, the Sonex Xenos involved in the Sept. 17, 2022, triple-fatal midair collision in Colorado was not transmitting ADS-B “out” data at the time of the accident, according to the NTSB. ADS-B “out” is required within the Denver Mode C veil where the accident occurred. And the NTSB Preliminary Report (download PDF here) further states the aircraft’s last flight during which it broadcast ADS-B data was flown on July 14, a flight lasting six minutes, according to FlightAware.
Between that date and the accident date, FlightAware (which gets its data from numerous sources, including air traffic control and ADS-B) recorded eight more flights originating from the Sonex’s home airport (Platte Valley Airpark—18V), which lies well within the Mode C veil. The flights ranged in duration from 12 minutes to just less than an hour.
Both aircraft involved in the accident, the Sonex and a Cessna 172 Skyhawk on a training flight with two on board, were squawking VFR (1200) transponder codes. According to the text of the NTSB report, “Both airplanes operated within the Mode-C veil of the Denver International Airport Class B airspace that required automatic dependent surveillance broadcast (ADS-B) ‘out’ transmissions. The Cessna was equipped with ADS-B ‘in/out’ equipment and transmitted ADS-B data during the accident flight. The Sonex did not transmit ADS-B data during the accident flight …” Neither aircraft was in radio contact with ATC, nor were they required to be.
From the report: “A review of air traffic control (ATC) flight track data revealed the Cessna departed Rocky Mountain Municipal Airport (BJC), Denver, Colorado, about 0843, and the Sonex departed Platte Valley Airpark (18V), Hudson, Colorado, about 0838. The airplanes climbed to about 7,000-7,500 feet mean sea level (msl) [approximately 2,000 feet above ground level] and were operating under visual flight rules (VFR). The Cessna flew northbound and the Sonex flew westbound toward the Longmont area. After the Cessna completed a left 360-degree turn, it turned eastbound. The flight track data of the two airplanes merged and subsequently showed both airplanes rapidly descending.”
The FAA-registered owner of the Sonex, Henry Butler Jr., was the pilot on the accident flight and the sole occupant. According to FAA records, the aircraft was registered on Feb. 24, 2022. The previously listed owner was a limited liability corporation in Wisconsin. The corporation was listed as the registered owner from August 2016 until October 2021 when the aircraft was listed as “Registration Pending.”
Thread
Thread Starter
Forum
Replies
Last Post