John Wiseman
@lemonodor
Followers
15K
Following
53K
Statuses
20K
Persistent sousveiller. Walt Disney R&D Imagineer. DM for Signal.
Los Angeles
Joined March 2007
Finally, the only daily, global, free map of GPS interference has officially launched: Watch jamming around conflict zones develop over time. Wonder who's jamming GPS all around Moscow. Like all the best maps, it raises more questions than it answers!
80
1K
4K
RT @trbrtc: The Pentagon has sent at least 18 surveillance flights of sophisticated spy planes to the Mexican border to collect intelligencā¦
0
34
0
@thenewarea51 @ADSBex @flightradar24 Yes, FR24 seems to switch to showing mlat positions when GPS is being spoofed.
I think FR24 quietly introduced an anti-GPS spoofing measure. Left: ADS-B Exchange map of AAL121 showing where it began being spoofed to Beirut Intl. Airport. Right: FR24 map showing where they FR24 switched to showing MLAT position *instead of the ADS-B position*.
0
1
2
RT @AJamesMcCarthy: Currently editing tonight's shot... and WOW. This is probably my new favorite ISS transit shot... beating out the oneā¦
0
1K
0
I am legally bound to repost all long-exposure photos of aircraft circling.
0
3
39
The day before the DCA crash a passenger jet aborted its landing due to a TCAS RA with a military helicopter. The NTSB referenced the incident in a briefing on the crash, saying it would be considered in the overall evaluation of the accident.
Washington DC - January 28th, 2025 POTOMAC DEPARTURE: BRICKYARD 4514, what was the reason for the go-around? BRICKYARD 4515: We had a RA with the helicopter traffic below us. Multiple signs that went unnoticed for many years The culprit was PAT01 and the runway in use was 19 at DCA Audio via @liveatc and Bill B.
1
1
1
@thenewarea51 When I moved from Chicago to LA, my two cats were under the seat in front of me. They were very chill.
0
0
1
@ShubertSomer @TaraCopp @NTSB I thought about trying to georeference the radar video but it's not easy to do accurately. This is my attempt to turn the inaccurate mlat positions into a more accurate track.
0
0
1
@ShubertSomer @TaraCopp @Hal9O0 @michellelprice @NTSB I think they were talking about the Blackhawk being at 200 at that point but they forgot to say that. it led to confusion throughout the rest of the briefing.
0
0
0
@ShubertSomer @TaraCopp @Hal9O0 @michellelprice @NTSB It was very confusing, but at 28:00: "The CRJ at the time of impact based on ADS-B data and the data in the flight recorder shows that that airplane was positioned at 325 feet +- 25 feet. On the radar scope in the cabā¦the Blackhawk helicopter would have visualized at 200 feet."
1
0
0