No, it shows them starting a descent. Look at the tracklog rather than he FlightAware graph.When the flight track ends, it's still at FL300, right? Is that inconsistent with a plane that would have ran out of fuel and slowly descended into terrain? The mountains in VA aren't very high.
Yeah, that is what I am wondering. If "began to break up" means that it was shot down.Look at the increase in speed. With that and an 8,000 fpm descent, I’m guessing it began to break up before it crashed, which would explain the loss of signal. I’m sure we’ll find out soon enough what caused it to finally depart from level flight.
The SFRA is stated to go to FL180. I'm not sure what one has to do to fly above that level, or if filed flight plans often (or ever) fly over the SFRA. I haven't paid much attention to that aspect since I'll never be in that situation and only needed to know the procedures to get into/out of the SFRADoes DC restricted airspace go above FL180?
Odd they were held at FL340 eastbound. Seems to have filed 390 per FlightAware?
Looks to me like it turned @ ISP instead of landing and decided to fly back home to 0A9. Didn't quite make it.Looks like it it flew the flight plan then turned and flew runway heading
Looks to me like it turned @ ISP instead of landing and decided to fly back home to 0A9. Didn't quite make it.
About 500 nm from 0A9 to ISP. Then flew back another 400 nm before rapid descent. Range of the aircraft is listed as about 2000 nm. But for a flight expected to be 500 nm (from 0A9 to ISP), what would be a normal fuel load or is there no such thing as a normal fuel load?
The flight plan wasn’t direct KISP, it ended in CCC KISP, presumably to pick up and instrument approach to runway 24. The autopilot flew the leg from the Calverton VOR to the airport, then continued in a straight line.Let’s say pilot is incapacitated. Auto pilot flying the plane. What could account for it hangin’ a 180 over destination and then just flying straight ahead, looking like back to departure point
No, where it crashed was SW of MOL VOR. Not in the least Northern Virginia.the SB was an F-16 respomding to an airspace violation. the target crashed in northern VA.
https://www.foxnews.com/us/washington-dc-area-explosion-sound-caused-military-jet-department-defense
It followed all the bends in the flight plan route that Flight Aware shows as their filed/assigned route. This took them south of the FRZ. When they got to ISP it seems that the thing went direct back to 0A9 (the departure point) which took them right through the FRZ.The flight plan wasn’t direct KISP, it ended in CCC KISP, presumably to pick up and instrument approach to runway 24. The autopilot flew the leg from the Calverton VOR to the airport, then continued in a straight line.
They went to guns, two shots, one for each tank (and don’t be f’ng up my punchline with how many tanks are in each wing)
Have flown several citations in the past. Some types have “EDM” (emergency descent mode). If the AP is engaged above FL310, and there is a rapid decompression, the airplane will automatically turn and descend without crew assistance.Anybody who flys these is that they way the autopilot works?? Looks like it it flew the flight plan then turned and flew runway heading
Assuming the plane is in ALT Hold mode with zero thrust, the AP is going to pitch the plane up into a stall. I do not think this model has anything that would disconnect the AP with stall warning. It does have over-torque disconnect.
They went to guns, two shots, one for each tank (and don’t be f’ng up my punchline with how many tanks are in each wing)
You’re right. My only defense is it was in response to the speculation that they actually shot him down which I considered sensationalist. But I said what I said and I’ll own it.A tasteless and inconsiderate post.
Making jokes about killing someone, at the expense of grieving families.