Ntsb Investigations logo

Ntsb Investigations

Search NTSB aviation investigations by aircraft, registration, date, state, or injury level through MCP.

Install Ntsb Investigations

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "ntsb-investigations": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ntsb-investigations"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 2 tools correctly (1d ago).

Overview

Ntsb Investigations searches NTSB aviation accident and incident records by tail number, aircraft make and model, date range, state, or injury level. Its two tools return investigation details such as event date, location, probable cause, findings, and a docket link. The keyless MCP endpoint reads a prepared copy of NTSB's public aviation database, making it suitable for research and targeted case lookup without an upstream account.

Use cases

  • Find investigations involving a specific aircraft registration
  • Compare accidents for an aircraft manufacturer or model
  • Identify aviation accidents by state and date range
  • Filter cases by fatal, serious, minor, or no reported injuries

Key features

  • Searches NTSB aviation investigations by registration or make
  • Filters by model, year, state, and injury level
  • Searches cross-make accidents over bounded date ranges
  • Returns probable cause, findings, and event details
  • Includes NTSB docket links
  • Uses a keyless MCP endpoint

Tools2

What Ntsb Investigations lets your agent do. Expand a tool for its parameters.

Verified live~901 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

5/5 checks healthy over the last 17d

What it can do

From the 2 tools this server returned when we ran it; 2 declare their own safety hints.

Makes network requests · 2Read-only tools · 2
Network at startup4 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age25 days
Maintainers1

Observed 2026-11-03 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 3d ago via OSV.dev · @pipeworx/mcp-ntsb-investigations (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads727Package downloads in the last 30 days.
Last commit1d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed2Callable tools this server registers over MCP.

How Ntsb Investigations works

What Ntsb Investigations does

Ntsb Investigations exposes searchable NTSB aviation accident and incident data through MCP. It covers aircraft investigations across manufacturers and can locate records using a registration number, make, model, event year, state, injury severity, or a date range.

Results can include the NTSB case number, event date, location, injury level, phase or occurrence, probable cause, findings, and a link to the corresponding NTSB docket. Registration searches preserve historical matches when an FAA tail number has been reassigned; each returned case retains its own aircraft and event details.

The integration is independent and unofficial. Its source data comes from NTSB's public eADMS aviation bulk dataset, while docket links point to NTSB's public docket pages.

How it works

The MCP endpoint is available at https://gateway.pipeworx.io/ntsb-investigations/mcp. Add that URL to an MCP client and invoke either search tool through the client interface. Authentication is not required, and no upstream NTSB account or API key is needed.

The underlying dataset is refreshed from NTSB's avall.zip bulk file. The refresh process extracts selected Access database tables, combines aircraft, event, narrative, findings, sequence, and data-dictionary records into case-oriented data, and stores indexes by make, registration, and year. Queries then read the relevant shard or year shards instead of processing the entire source file for every request.

Responses include metadata such as the source, record count, query details, and the date of the data refresh. That data_as_of value identifies the refresh date rather than an individual record's publication or event date.

Setup and configuration

Register the endpoint in an MCP client with a configuration similar to:

config.json
{
  "mcpServers": {
    "ntsb-investigations": {
      "url": "https://gateway.pipeworx.io/ntsb-investigations/mcp"
    }
  }
}

The endpoint can be added to Claude Desktop, Cursor, or Windsurf. No environment variables, credentials, or client-side API keys are needed for the documented connection.

Tools and capabilities

  • ntsb_search_investigations searches by registration or make, with optional model, year, state, injury_level, and limit filters. A model filter narrows within a make using prefix matching, so values such as 172 can match related model variants.
  • ntsb_accidents_by_period searches across all aircraft makes using inclusive from and optional to dates. Dates accept year, year-month, or full-date formats and can be filtered by state and injury level.
  • Period searches return results, a match count, truncation status, and counts grouped by state. The state grouping covers all matches even when the result list is limited.
  • Search results can link an investigation to its NTSB docket, where final reports and supporting documents are published.

Limitations and notes

ntsb_search_investigations requires either a registration or a make. A reused registration may return multiple aircraft histories; provide a year when a particular incarnation is needed.

Some broad makes are split across yearly data shards. Queries for those makes without a model or year may be rejected when they would require too many shard reads; adding a year or more specific make/model query narrows the request.

ntsb_accidents_by_period accepts ranges spanning no more than eight calendar years. It reads one year index per calendar year, then applies state and injury filters. Narrow a longer request before submitting it.

The endpoint also exposes shared Pipeworx gateway tools in addition to the two NTSB-specific tools, so an MCP client may display more tools than those listed here.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Ntsb Investigations

Ntsb Investigations is an MCP server that connects AI clients to a searchable copy of the NTSB aviation accident and incident database. Its main tools, ntsb_search_investigations and ntsb_accidents_by_period, find cases by aircraft details, date, state, or injury level and return case facts plus docket links.

Add the endpoint URL to your MCP client's server configuration. Use `https://gateway.pipeworx.io/ntsb-investigations/mcp` under the `ntsb-investigations` server name; the connection requires no API key, upstream account, or environment variables.

Yes, Ntsb Investigations works with Cursor through its MCP server URL. Add `https://gateway.pipeworx.io/ntsb-investigations/mcp` to Cursor's MCP configuration, then use the NTSB search tools from the client.

Yes, use `ntsb_accidents_by_period` for cross-make searches. Supply an inclusive date range and optionally filter by state or injury level; ranges longer than eight calendar years must be narrowed.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewNtsb Investigations AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/ntsb-investigations?style=directory)](https://allmcps.com/mcp/ntsb-investigations)
HTML Embed
<a href="https://allmcps.com/mcp/ntsb-investigations"><img src="https://allmcps.com/api/badge/ntsb-investigations?style=directory" alt="Ntsb Investigations on AllMCPs" /></a>