AIS-SART Alert

[NR857]

Send an alert when an AIS SART is activated within a receiving station's coverage area

[NR857]

AIS SART's have MMSI's commencing 970, so perhaps that string could be used to identify activations. I'm new to programming and Github etc, so I don't know how to this yet lol

[NR857]

https://cdn.standards.iteh.ai/samples/16694/7bf752a5752548be8abe3a3b90f71445/IEC-61097-14-2010.pdf

[NR857]

Online AIS SART NMEA message decoder. May be useful

https://rl.se/aivdm

[jvde-github]

Thanks both. I had a test with the following NMEA line from here:

 !AIVDM,1,1,,B,1>MA>E>P000NoHHMEB=P0?wt1t00,0*4C

It did not display as a AIS-SART alert if I give this as text input. The idea was that it shows like a SART/EPIRB with country code 970. I fixed that and uploaded the fix. Now it will look like this:

Next question is what kind of alert are you thinking about? I am thinking that it could be easier to add to the site version (aiscatcher.org) as that is permanently running and we can create email alerts for regions.

On the command line you can capture AIS-SART active messages with:

AIS-catcher  -o 5  | grep \"status\":14

It seems though these might not only come from MMSI 970 but also from more regular MMSI. I guess there is a difference between the message SART and the device. Need to read into that.

[jvde-github]

Yes, 970 is the device and status 14 is typically used if a SAR is in progress. So red diamond will only tell you if it comes from a SAR device. I guess the messages with status 14 is more interesting to monitor?

For example, I see currently a few ships emitting this message. For example this one on aiscatcher.org:

and in MarineTraffic:

[NR857]

I didn't notice that. Which means that the Catcher already identifies the AIS SART class. What's needed to send a push notification or popup when one is activated? Under the regulations SARTs are required to be tested regularly I have seen alerts for tests on Boat Beacon, but obviously you will see more alerts in heavy traffic areas such as Gibraltar Straits which is not too far from here.

Agreed email alert on Web would be great.

All very interesting!

[NR857]

Yes I think a mail might bve easiest?

[NR857]

Ok if the MOB or crew activate an AIS SART, a different matter if it's 406 or 121.5

[jvde-github]

I started a simple page (for now) that tracks ships for which the status is changing to SAR/Aground/Not Under Command. Let's see how this will populate over time and how we can build on this.

https://aiscatcher.org/alerts

[jvde-github]

I removed the "Not under command" alerts, is not an interesting event. But at the same time added a list to track status changes for particular ships. For example the Dali.

[NR857]

Noted: ELLI GLITSCHER 211413680 reported "Aground" 15:50Z Hamburg

https://aiscatcher.org/alerts

Nice work

[jvde-github]

I think you can hover of it but this is receipt of message type 9, which is send by airplanes.

https://gpsd.gitlab.io/gpsd/AIVDM.html#_type_9_standard_sar_aircraft_position_report

[NR857]

Noted: ELLI GLITSCHER 211413680 reported "Aground" 15:50Z Hamburg

https://aiscatcher.org/alerts

Nice work

[NR857]

Re SAR aircraft

Some use "111" ahead of the country code, followed by an identifier.

i.e. SAR 111232532 airborne 4 minutes ago over Scotland or SAR 111257007, airborne now over Råde, Norway.

Spanish SAR helicopters sometimes use callsign "HELIMER" and also the 111 designator, followed by country code 224, then three digit identifier. You can find these on any of the public sources Marinetraffic, Vesselfinder, AISHUB etc

Irish SAR aircraft use SAR, tgen 250, such as SAR 250002898, currently airborne off south east Ireland.

[NR857]

A peculiarity of Irish and UK coastguard organisations is that they regularly carry out mountain rescue, snow relief and inland air ambulance missions- watch out for them!

[jvde-github]

I looked at the alerts again, think we need to make it a bit more exclusive, eg only from larger vessels etc

[jvde-github]

True....

[g7ruh]

Could also consider identifying SAR heli squawk code: "0023 Aircraft engaged in actual SAR Operations" from the ADSB message if you have access to ADSB decode data, e.g. take the data feed into AIS-catcher and monitor for specific squawk codes. Or write a AIS-catcher utility to parse the data and only feed the selected codes to AIS-catcher. That would save burdening AIS-catcher with mostly "useless" data with respect to ship tracking.

Apart from non-sea missions, also training as per here, lowering man onto deck training. Apologies Jasper, this was from before I had AIS-catcher!

[jvde-github]

For that the ais2adsb project might be interesting in combination with Virtual Radar Server. Also worked recently with the author of tar1090 to get ships in the ADSB viewer.

I will close this item. Base logic is implement. We can always open a new issue if there are some new ideas.

Thanks all.

[NR857]

👍

El vie., 17 may. 2024 18:56, Jasper @.***> escribió:

For that the ais2adsb project might be interesting in combination with Virtual Radar Server. Also worked recently with the author of tar1090 to get ships in the ADSB viewer.

I will close this item. Base logic is implement. We can always open a new issue if there are some new ideas.

Thanks all.

— Reply to this email directly, view it on GitHub https://github.com/jvde-github/AIS-catcher/issues/256#issuecomment-2118011276, or unsubscribe https://github.com/notifications/unsubscribe-auth/BH3OCY3ZLRRUUB2BLXAO6V3ZCYZEDAVCNFSM6AAAAABGIX4J4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJYGAYTCMRXGY . You are receiving this because you were mentioned.Message ID: @.***>