Talk:2023 Virginia plane crash

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Duplicate article Elkman (Elkspeak) 17:00, 5 June 2023 (UTC)[reply]

  • Support as 2023 Virginia plane crash editor. This stub contains very little information and the article should primarily cover the aviation incident. The intercept is important but secondary. Ppt91talk 17:13, 5 June 2023 (UTC)[reply]
  • Merged as article creator and only contributor of substantial content. ☆ Bri (talk) 17:39, 5 June 2023 (UTC)[reply]

Please, add ADS-B lat 40.48 & long -73.80, 19.5 mi from One World Trade (& airspeed at 1WT)[edit]

BilCat requested this topic be added to this talk page. |url=https://flightaware.com/live/flight/N611VG/history/20230604/1700Z/0A9/KISP/tracklog |title=FlightAware Flight Track Log [...] ADS-B

Pasting "403 kts to mph" gives 463.764118 mph. The coordinates on the World Trade Center (2001-present) page are in degrees, minutes & seconds. Converting them to decimal gives 19.5 miles. 19.5÷463.764118x60x60=151.3 seconds from 1 World Trade. It's merely very simple arithmetic, based on data in FlightAware's ADS-B track log. Alternatively, if people were inclined, they could crudely measure the 19.5 miles from an image of the flight path from |url=https://www.fox5dc.com/news/cessna-plane-crashes-into-mountainous-terrain-in-southwest-virginia 50.204.200.142 (talk) 00:16, 7 June 2023 (UTC)[reply]

Why does it matter how far away from the world trade center it was? Many places have flew right past WTC and the pilots were terrorists PalauanLibertarian🗣️ 01:38, 7 June 2023 (UTC)[reply]
  • Weren't terroists
PalauanLibertarian🗣️ 13:02, 7 June 2023 (UTC)[reply]

Exact coords[edit]

Does anyone have the exact coordinates. I know its near St. Mary's Wilderness, but do we have coordinates. Sentinel-2 hasn't passed over the area yet but when it does I'll check to see if I can find the crash. PalauanLibertarian🗣️ 01:41, 7 June 2023 (UTC)[reply]

According to this story from Staunton News Leader, it is 300 feet below the peak of a mountain they locate on a map. I've correlated the peak to Mine Bank Mountain. Coordinates according to USGS are 37°55′7.46″N 79°6′0.09″W / 37.9187389°N 79.1000250°W / 37.9187389; -79.1000250Bri (talk) 03:12, 7 June 2023 (UTC)[reply]
Thanks, I'll wait until Sentinel-2 passes it so we can get some satellite imagery PalauanLibertarian🗣️ 13:00, 7 June 2023 (UTC)[reply]
@Bri Unfortunately, you cant see much in the satellite image.
PalauanLibertarian🗣️ 13:24, 8 June 2023 (UTC)[reply]
I expected it to be hard to find, basically you're trying to find a Cessna-sized hole in the forest canopy. There's an aerial image in the press today (scroll down to still image #4 with the crash site in a red circle), looks like it's from a helo near ground level and even then it's hard to see. ☆ Bri (talk) 19:16, 8 June 2023 (UTC)[reply]
The same publication printed this story yesterday, confirming the location is "at an elevation of just over 2,700 feet on the north side of Mine Bank Mountain." ☆ Bri (talk) 03:24, 7 June 2023 (UTC)[reply]

Flight Plan and Path[edit]

The aircraft filed, was cleared for and flew the following route:

0A9 PSK GVE SIE BRIGS Q439 SARDI CCC KISP

Filed flight level: FL390

The route took the aircraft through the DC restricted area on its way TO its destination of KISP. The pilot was not in communication with ATC prior to entering the restricted airspace the first time. ATC cleared the aircraft to FL310 but the pilot never responded. Most likely, based on distance from departure airport and the DC restricted area, this aircraft would make FL310 well before DC. The plane did level at a higher, unassigned altitude.

Why was the national guard not notified during the FIRST flight through DC restricted airspace?

Why only after the second violation of the space?

The aircraft most likely wasn’t heading back to its departure airport when it crashed Best probablility it was on a track based on the final track inbound to KISP from CCC Most likely coincidental.

2600:100B:B127:3B1B:7C30:A14E:733:35BC (talk) 00:48, 22 July 2023 (UTC)[reply]