The question of jurisdictional authority over military aviation accidents represents one of the more consequential fault lines in United States aviation safety oversight. The short answer is that the NTSB and FAA generally do not investigate military aircraft accidents. Under 49 U.S.C. § 1132, NTSB authority extends to civil aircraft, and military aircraft are explicitly excluded from that definition. Each branch of the armed forces maintains its own independent accident investigation infrastructure: the Army Safety Center at Fort Novosel, the Naval Safety Command in Norfolk, the Air Force Safety Center at Kirtland AFB, and equivalent organizations within the Marine Corps, Coast Guard, and Space Force. These agencies conduct their own investigations under service-specific regulations such as Air Force Instruction 91-204 and Army Regulation 385-10, following processes that are structurally analogous to — but legally separate from — the civilian NTSB model.
The military investigation framework bifurcates into two distinct board types that civilian pilots and operators should understand when consuming accident reporting. The Safety Investigation Board (SIB) produces a privileged, non-punitive report intended solely for safety improvement and is expressly protected from release or use in legal proceedings — a direct analog to the NTSB's own safety recommendation philosophy. The Accident Investigation Board (AIB), by contrast, produces a non-privileged factual record that can support administrative or legal action. This dual-track system allows frank safety analysis to proceed without the chilling effect of legal liability, mirroring the reasoning behind protections afforded to aviation safety action programs (ASAP) and flight operational quality assurance (FOQA) data in the civilian world. The classified nature of military platforms, weapons systems, and tactics is addressed through the privilege doctrine itself — sensitive technical data appearing in SIB reports is redacted or withheld under national security authority before any public release occurs.
There are narrow but operationally significant exceptions where the FAA does retain jurisdiction over military personnel. If a military aviator holds a civilian airman certificate — and many do, particularly those pursuing airline careers — the FAA can take certificate action based on conduct that would constitute a violation of the Federal Aviation Regulations, regardless of whether the incident involved a military aircraft operating under military flight rules. Additionally, when a military aircraft operates in civil airspace under instrument flight rules using ATC services and is involved in a mid-air or near-miss with a civil aircraft, the FAA's Air Traffic Organization will conduct its own review of the ATC component, and the NTSB may investigate the civilian aircraft side of the occurrence independently. These overlapping jurisdictional edges matter to corporate and airline flight departments whose aircraft routinely share busy terminal areas and en route airspace with military traffic.
For professional operators, the broader relevance of the military investigation system lies in what safety data does and does not flow into the civilian knowledge base. Military accident findings are frequently published in sanitized form through branch safety magazines — Flightfax, Approach, and Flying Safety — and some findings eventually migrate into civilian safety culture through shared venues such as the Flight Safety Foundation and joint FAA-DoD working groups. However, the classification barrier means that systemic failures in advanced military platforms, from avionics integration problems to human factors issues in high-g maneuvering environments, rarely receive the same level of public technical scrutiny that a comparable civil accident would generate through an NTSB docket. For pilots flying near military operating areas, restricted airspace, and MOAs, awareness of this information asymmetry reinforces the importance of rigorous preflight review of NOTAM structures and published MOA activity schedules rather than assuming full situational awareness through conventional open-source channels.