RAIM Prediction

Required roles: AIS PIB API — Roles
Base endpoint: https://ais-pib-api.ibosoft.net.tr:2087/raim-prediction
Reference documents: none
Attribution: show ibonav.aero wherever this data is displayed
Data sources: EUROCONTROL AUGUR.
Last updated: 17 OCT 2026

Depending on your use, the original data sources may also need to be credited.

GNSS RAIM (receiver autonomous integrity monitoring) outage prediction for aerodromes or a whole FIR on a given day: the periods in which RAIM is predicted to be unavailable for the chosen flight phase and receiver settings.

A PBN operation that relies on GNSS without augmentation needs RAIM to be available. Use this service in pre-flight planning to check, for the departure, destination and alternate aerodromes or for the FIRs on the route, whether RAIM outages are predicted during the flight; if so, plan another time, another procedure or another means of navigation.

The prediction is calculated for each request (nothing is stored), so a request can take up to about a minute and requests are answered one at a time. Predictions exist only for the current window of about 72 hours; for other dates the answer has a notice and no results.

Endpoints

Endpoint Description
GET /raim-prediction/locations Aerodromes and FIRs that can be predicted
POST /raim-prediction/predict RAIM outage prediction

Parameters

/predict (JSON body)

Field Required Default Description
prediction_date yes — Day of the prediction, YYYY-MM-DD (UTC)
airports one of the two — Up to 5 ICAO location indicators of aerodromes (from /locations)
fir one of the two — ICAO location indicator of one FIR (from /locations); all its aerodromes are predicted
flight_phase no approach_rnp03 approach_rnp03 (approach, RNP 0.3), approach_rnp01 (approach, RNP 0.1), terminal_rnp10 (terminal, RNP 1.0)
algorithm no FD Receiver RAIM: FD (fault detection) or FDE (fault detection and exclusion)
mask_angle no 5.0 Receiver mask angle in degrees: 2.0, 5.0, 7.5, 10.0, 12.5
baro_aiding no false true: the receiver uses barometric aiding
selective_availability no true true: the receiver assumes selective availability (as in older receivers' RAIM)
egnos_notams no false true: also take EGNOS NOTAMs into account

airports and fir cannot be used together. Choose the settings that match the aircraft's GNSS receiver (see its flight manual or receiver documentation).

{
  "prediction_date": "2026-10-17",
  "airports": ["LTFM", "LTAI", "EDDF"],
  "flight_phase": "approach_rnp03",
  "algorithm": "FDE",
  "mask_angle": 5.0
}

Response

/locations

{"airports": ["EDDF", "LTAI", "LTFM", "…"], "firs": ["EDGG", "LTAA", "…"]}

The list changes rarely; it is refreshed daily.

/predict

{
  "scenario": {"begin": "2026-10-17T00:00:00", "end": "2026-10-18T00:00:00"},
  "results": [
    {"icao": "LTFM", "name": "ISTANBUL AIRPORT", "has_outages": true,
     "outages": [{"begin": "2026-10-17T03:12:00", "end": "2026-10-17T03:19:00", "duration_minutes": 7}]},
    {"icao": "LTAI", "name": "ANTALYA", "has_outages": false, "outages": []}
  ],
  "notice": null
}
Field Description
scenario Period covered by the prediction (UTC)
results[].has_outages true when at least one outage is predicted
results[].outages Predicted outage periods: begin, end (UTC) and duration_minutes
notice Explanation when there are no results (e.g. the date is outside the prediction window); otherwise null

Errors

Code Meaning
422 Invalid body: wrong date format, more than 5 aerodromes, invalid location indicator, both or neither of airports and fir, or a value not in the lists above
500 The prediction could not be produced
502 The prediction service could not be reached
504 The prediction took too long; retry later