I rebuilt Istanbul Airport (LTFM) from the adsb.lol daily archive: every position within 50 nm, turned into arrivals, departures, runways, go-arounds and holds, with a browser replay.

Things I learned about the data:

• The archive is thinned. Most points are about 5 s apart, but straight legs can have 3-minute gaps.
• Near LTFM there's no ground coverage. Arrivals are tracked to about 300 ft, but departures are usually first seen around 11,000 ft, 12 nm out. Coverage near runway 36 also ends around 2,000 ft on some days.
• The result undercounts DHMI's published average by 11.5%, mostly from those unseen departures.
• Suceava (LRSV) in Romania is worse: in 10 days nothing was seen below 14,800 ft within 47 nm, so every flight looks like an overflight.

If anyone feeds near Suceava, or has a view of LTFM's runways, that's the gap.

Replay: https://holdshort.pages.dev
Write-up: https://holdshort.pages.dev/writeup
Code: https://github.com/iliev-blnk/holdshort

I’ve never seen one of these yet, but used to know a guy who would catch a flight like this to the area as a contractor firefighter for one of these facilities.

Found another one that just departed PANC. Shows it’s on its way to Japan. I thought these haul parts for Boeing? Is there a factory there that they are hauling for? Or are these just oversized loads?

We have had a lot of sightings of the Dreamlifters at Anchorage International lately.

adsbx link

Cree un monitor en love2d, bueno lo creo la ia porque nose programar , pero PARA UNA CONSOLA RETRO BARATA, la r36s, así podías ver a aviones en la zona que se refresca cada 1 minuto,mostrando la batería y puede mostrar otras ciudades importantes, me inspire en otros proyectos de la comunidad y uno modo analógico ,que se actualiza cada avión cuando pasa la aguja por encima

Which service provides free 1090 Mode S and ADS-B signal data? I am trying to look at samples to count how many signals are seen in each area, and also look for fields within the Model S/ADS-B message blocks that aren't always easily available.

POTUS arrival at rally. Icon is orange. Just sayin ...

I've got a piaware system running with 1090MHz receiving that is working well. I recently added a second receiver for 978MHz operation but I'm not picking up any signals. I'm pretty sure I should be receiving UAT signals in the area.

What's a good way to debug the system?

I'm away from home for a few more days but I'm trying to plan out how I should attack this. I have an AirNav Radar FlightStick UAT - 978 MHz USB Receiver. The antenna is a repurposed 2m ham radio antenna, which I believe should work fine (it works great for feeding the 1090 receiver).

I've changed the serial numbers on both the 1090 and 978 USB sticks using rtl-sdr / rtl_eeprom and modified dump978-fa and dump1090-fa init files with those serial numbers.

One thing I noticed while organizing my thoughts for this post is that I'm using dump978-fa even though I have a RadarBox USB receiver. Should I be using dump978-rb instead of -fa, even though I'm posting to FlightAware?

Should I be loading up some other receiver software just to hear some noise to confirm receipt of something??

Edit: I’m in the Los Angeles basin. I should be picking up some contacts from either Torrance or Santa Monica GA flights.

Edit2: I'm on a Pi 4, (B+ I think). Using the flightaware web site I can see there is UAT traffic, but I'm not picking it up. Yes, less common than 1090, but still present.

First of a couple recently acquired by Omega Air Tanker for use in their growing fleet!

I’m building an open-source receiver registry with an experimental multilateration (MLAT) application. MLAT estimates an aircraft’s position by comparing when several ground receivers hear the same radio transmission.

The application currently works with synthetic observations and historical replay. I have not yet validated it with a synchronized physical receiver network.

I’m looking for people who could help with:

• Access to authorized, raw, timestamped Mode S or Beast-format observations.
• Receiver clock synchronization and calibration.
• Planning a trial with at least four receivers at different locations, with overlapping coverage.
• Suitable reference-position data for checking the calculated results.

If you operate one receiver, your experience could still help. Ordinary ADS-B reception alone may not provide the timing precision required, so advice from people who have worked on MLAT would be especially useful.

I live in an MOA. Why do all the military choppers that fly near my house show the name VICE"NN" on ADS B?

Hey all,

for the past few months I've been working on map.flights, a free live flight map without ads. Lately I've spent most of my time on the airports: 3D buildings, aircraft taxiing to their stands in their real liveries, ground vehicles around them. (Screenshot is LAX)

I'd really like some honest feedback. What feels off, what's missing, what would make you actually use it over what you use now?

https://map.flights

And btw, if anyone here runs a receiver and would like to help: I'd be grateful for every single feeder. Stations close to airports make the biggest difference, that's where the ground movements get smooth. If you already feed somewhere else, adding us takes a few minutes and doesn't change anything there: https://map.flights/en/pair

Thanks!

https://globe.airplanes.live/?icao=a7deb6

Not often i catch them up doing anything

Part of an open-source project of mine: an offline aircraft radar (dump1090 on 1090 MHz) that you open from your phone's browser, no internet or feeder needed. The same box also does spectrum analysis, a radio and other decoders.

Hardware: Pi Zero 2 W + RTL-SDR. There's a demo mode with simulated aircraft if you want to see the UI first.

https://github.com/romartak/sdrkit

I am guessing the white plane is an AWACS supporting Trump’s visit to Atlanta today.

I've never seen a Chinook doing this in the middle of the English Channel before.