Guide · 3 Verified sources

Track UK air, rail and marine accident investigation reports

Monitor the AAIB, RAIB and MAIB report feeds on GOV.UK and get an alert for each newly published investigation report, bulletin or safety digest, and each update to one.

Start with UK air accident investigation reports REST API, CLI and MCP

The problem

The UK has three accident investigation branches. The Air Accidents Investigation Branch (AAIB) investigates civil aircraft accidents and serious incidents in and over the UK, including drones. The Rail Accident Investigation Branch (RAIB) investigates accidents and incidents on railways and tramways. The Marine Accident Investigation Branch (MAIB) publishes notices in its own feed. Each publishes on GOV.UK, which provides the collection as an Atom feed.

If you follow these investigations for an operator, an insurer or a newsroom, the work is noticing the day a report appears or is revised. This guide sets up one monitor per branch, each record keyed by GOV.UK's feed identifier.

What the source contains

UK air accident investigation reports · Air Accidents Investigation Branch

Air Accidents Investigation Branch investigation reports from GOV.UK's feed, one record per report: aircraft type and registration in the title, and what happened, where and when in the summary.

5 typed fields · 50 records in SourceFinch's latest run on October 12, 2026 · publisher updates: several times a month · full source page

Field	Type	Description	Sample value
`id`key	string	GOV.UK feed entry identifier (a tag: URI naming the document's path), stable across revisions. The record key.	tag:www.gov.uk,2005:/aaib-reports/aaib-investigation-to-zenair-ch-601hds-g-chzs
`title`	string	Title of the investigation report as published on GOV.UK.	AAIB investigation to Zenair CH 601HDS, G-CHZS
`url`	url	Link to the document on GOV.UK; the linked page and its attachments are not fetched.	https://www.gov.uk/aaib-reports/aaib-investigation-to-zenair-ch-601hds-g-chzs
`updated_at`	datetime	Time GOV.UK last published a change to the document, with its UTC offset; not the date of the underlying event.	2026-10-08T10:00:12+01:00
`summary`	string, nullable	Short summary from the feed, when GOV.UK provides one; linked document bodies are not collected.	Hard landing after engine failure, Tatenhill Airfield, Staffordshire, 22 April 2025

UK rail accident investigation reports · Rail Accident Investigation Branch

Rail Accident Investigation Branch investigation reports, interim reports and safety digests from GOV.UK's feed, one record per document, with the location and date of the occurrence in the summary.

5 typed fields · 50 records in SourceFinch's latest run on October 12, 2026 · publisher updates: several times a month · full source page

Fields and a sample record

Field	Type	Description	Sample value
`id`key	string	GOV.UK feed entry identifier (a tag: URI naming the document's path), stable across revisions. The record key.	tag:www.gov.uk,2005:/raib-reports/report-11-slash-2026-unsafe-movement-of-locomotives-being-coupled-on-the-bluebell-railway
`title`	string	Title of the report or safety digest as published on GOV.UK.	Report 11/2026: Unsafe movement of locomotives being coupled on the Bluebell Railway
`url`	url	Link to the document on GOV.UK; the linked page and its attachments are not fetched.	https://www.gov.uk/raib-reports/report-11-slash-2026-unsafe-movement-of-locomotives-being-coupled-on-the-bluebell-railway
`updated_at`	datetime	Time GOV.UK last published a change to the document, with its UTC offset; not the date of the underlying event.	2026-10-08T11:01:41+01:00
`summary`	string, nullable	Short summary from the feed, when GOV.UK provides one; linked document bodies are not collected.	Unsafe movement of locomotives being coupled on the Bluebell Railway, East Sussex, 9 August 2025.

Recent marine accident report notices · Marine Accident Investigation Branch

Monitor publisher feed notices with native identifiers, titles, links and revision timestamps. Preserve the exact current feed as evidence of later changes.

5 typed fields · 50 records in SourceFinch's latest run on October 12, 2026 · publisher updates: current publisher feed; monitor hourly · full source page

Fields and a sample record

Field	Type	Description	Sample value
`id`key	string	Native publisher feed identifier, stable across revisions to the notice.	tag:www.gov.uk,2005:/maib-reports/fatal-accident-to-a-crew-member-on-board-the-bermuda-registered-passenger-vessel-arvia
`title`	string	Publisher notice title; does not establish an enforcement finding.	Fatal accident to a crew member on board the Bermuda registered passenger vessel Arvia
`url`	url	Publisher link to the notice; the linked document is not fetched.	https://www.gov.uk/maib-reports/fatal-accident-to-a-crew-member-on-board-the-bermuda-registered-passenger-vessel-arvia
`updated_at`	datetime	Publisher revision time in UTC; not an incident or first-publication date.	2026-10-08T09:59:31+01:00
`summary`	string, nullable	Publisher feed summary only; linked article bodies are not collected.	Location: on passage from Southampton, England, to Santa Cruz de Tenerife, Canary Islands, Spain.

What a change means

A new id: a newly published document. For AAIB, title carries the aircraft type and registration mark and summary the occurrence, place and date; for RAIB, summary gives the place and date of the occurrence.
A change to updated_at on an id you already have: GOV.UK published a revision. It is not the date of the accident or incident.

Set it up in the console

Open the Verified recipe. Open the UK air accident investigation reports recipe in the console. It keeps the reviewed URL, fields and record key (id), and shows the latest captured sample. Open in the console
Create the monitor. Name the monitor, keep the daily schedule or pick another (the console shows the monthly run cost), confirm that you have the right to monitor the source, and choose Create monitor.
Run the baseline. The first run is the baseline: every record is new. From the second run on, the monitor reports what was added, changed or removed, field by field, with the evidence behind each value.
Choose how you hear about changes. In Alerts, choose immediate change emails or a daily or weekly digest; each monitor can override that on its own page. For your own systems, add a signed webhook in Destinations. Alerts and team
Add the RAIB and MAIB monitors. Open the rail and marine recipes the same way, or keep only the branch you follow. The marine recipe runs hourly; the air and rail recipes run daily.

The other recipes: UK rail accident investigation reports, Recent marine accident report notices.

The same through the REST API, CLI or MCP

Every surface creates the same monitor from the same Verified recipe. You confirm you have the right to collect the source (rights: true).

UK air accident investigation reports

REST API

Create an API key under Console → API & access. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/govuk-aaib-reports -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get govuk-aaib-reports --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor UK air accident investigation reports: get_catalog_source govuk-aaib-reports,
then create_source with its create_source_args (dry run first), then run_source."

source.json

The request body the API and CLI examples send.

{
  "name": "UK air accident investigation reports",
  "url": "https://www.gov.uk/aaib-reports.atom",
  "recipe": {
    "mode": "http",
    "format": "xml",
    "items": "entry",
    "fields": {
      "id": "id",
      "url": "link[rel=\"alternate\"]@href",
      "title": "title",
      "summary": "summary",
      "updated_at": "updated"
    },
    "required": [
      "id",
      "title",
      "url",
      "updated_at"
    ],
    "types": {
      "updated_at": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "govuk-aaib-reports",
    "version_id": "54efb3a6-6c33-42fd-9c34-a27161d2aa7b"
  }
}

UK rail accident investigation reports

REST API

Create an API key under Console → API & access. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/govuk-raib-reports -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get govuk-raib-reports --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor UK rail accident investigation reports: get_catalog_source govuk-raib-reports,
then create_source with its create_source_args (dry run first), then run_source."

source.json

The request body the API and CLI examples send.

{
  "name": "UK rail accident investigation reports",
  "url": "https://www.gov.uk/raib-reports.atom",
  "recipe": {
    "mode": "http",
    "format": "xml",
    "items": "entry",
    "fields": {
      "id": "id",
      "url": "link[rel=\"alternate\"]@href",
      "title": "title",
      "summary": "summary",
      "updated_at": "updated"
    },
    "required": [
      "id",
      "title",
      "url",
      "updated_at"
    ],
    "types": {
      "updated_at": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "daily",
  "rights": true,
  "catalog": {
    "slug": "govuk-raib-reports",
    "version_id": "29a43991-cc99-4393-a8ca-078f3ac29961"
  }
}

Recent marine accident report notices

REST API

Create an API key under Console → API & access. Reference: /docs/api.

# the Verified entry (fields, recipe, sample, terms) as JSON
curl https://sourcefinch.com/v1/catalog/govuk-maib-reports -H "Authorization: Bearer $SOURCEFINCH_API_KEY"

# create the monitor from source.json (below)
curl -X POST https://sourcefinch.com/v1/sources \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @source.json

# then run it now (later runs follow the schedule)
curl -X POST https://sourcefinch.com/v1/sources/$SOURCE_ID/runs \
  -H "Authorization: Bearer $SOURCEFINCH_API_KEY" \
  -H "Idempotency-Key: $(uuidgen)"

CLI

The sourcefinch CLI is not on npm yet; see /docs/cli.

sourcefinch login
sourcefinch catalog get govuk-maib-reports --source-json > source.json
sourcefinch sources create --file source.json
sourcefinch runs create $SOURCE_ID --wait
sourcefinch records $SOURCE_ID

MCP

Remote MCP server with OAuth; see /docs/mcp.

claude mcp add --transport http sourcefinch https://sourcefinch.com/mcp

# then ask your agent:
"Use SourceFinch to monitor Recent marine accident report notices: get_catalog_source govuk-maib-reports,
then create_source with its create_source_args (dry run first), then run_source."

source.json

The request body the API and CLI examples send.

{
  "name": "Recent marine accident report notices",
  "url": "https://www.gov.uk/maib-reports.atom",
  "recipe": {
    "mode": "http",
    "format": "xml",
    "items": "entry",
    "fields": {
      "id": "id",
      "url": "link[rel=\"alternate\"]@href",
      "title": "title",
      "summary": "summary",
      "updated_at": "updated"
    },
    "required": [
      "id",
      "title",
      "url",
      "updated_at"
    ],
    "types": {
      "updated_at": "datetime"
    }
  },
  "key_field": "id",
  "schedule": "hourly",
  "rights": true,
  "catalog": {
    "slug": "govuk-maib-reports",
    "version_id": "dc050655-b241-4b0f-b06d-d205b1579dd3"
  }
}

Alerts and evidence

AAIB and RAIB publish several times a month, so an immediate change email keeps you current without much noise. A weekly digest suits a reading list.

Every run keeps the publisher's exact response with its SHA-256 hash and a signed manifest, and every value points back to where it was read. How that works is in the docs:

Limitations

The AAIB and RAIB feeds carry the 50 most recently published or updated documents, and the MAIB feed is a current window, not a complete historical archive. An entry leaving a feed is not a withdrawal.
Report texts and attachments are not fetched. Titles and summaries identify aircraft, places and events, not the people involved, and MAIB crew details are not fetched.
A record says a document was published or revised. A title does not establish a finding; the findings are in the report on GOV.UK.
SourceFinch carries the feeds as published and adds no safety advice.

Usage rights, terms posture and reliability for each source are on its source page. They are our documented understanding of each publisher's stated terms, not legal advice.

SourceFinch is independent and is not affiliated with or endorsed by Air Accidents Investigation Branch, Rail Accident Investigation Branch, Marine Accident Investigation Branch. This guide describes their public data as SourceFinch acquires it. It is not legal, medical or financial advice.

Track UK air, rail and marine accident investigation reports

The problem

What the source contains

UK air accident investigation reports · Air Accidents Investigation Branch

UK rail accident investigation reports · Rail Accident Investigation Branch

Recent marine accident report notices · Marine Accident Investigation Branch

What a change means

Set it up in the console

The same through the REST API, CLI or MCP

UK air accident investigation reports

REST API

CLI

MCP

source.json

REST API

CLI

MCP

source.json

REST API

CLI

MCP

source.json

Alerts and evidence

Limitations

Related

Sources

Publishers and categories

Other guides