Hurt on a flight? Start a free case evaluation
RESQ.com. When your future is at stake. (800) 300-0001 Free case evaluation Call Now
US Aircraft Accidents: How to Verify Records, Understand Investigations, and Protect Injury Information

Home / Blog / us aircraft accidents

US Aircraft Accidents: How to Verify Records, Understand Investigations, and Protect Injury Information

Published by The Ledger Law Firm · · general information, not legal advice

What qualifies as a U.S. aircraft accident

A U.S. aircraft accident is an aircraft-operation occurrence that happens between boarding with the intention of flight and disembarkation, and involves a death, serious injury, or substantial aircraft damage.

The NTSB definition excludes several listed minor or component-damage examples.

Aircraft reporting rules also capture some events that may not fit the accident definition. Property damage other than damage to the aircraft estimated to exceed $25,000 for repair, or the fair-market value in a total loss, whichever is less, is among the FAA’s listed occurrences requiring notification. In the NTSB’s CY 2018 summary, general aviation recorded 1,275 accidents, 224 fatal accidents, and 379 fatalities; those figures describe that historical year and category, not a current national count. A cited analysis found that general aviation aircraft were involved in almost 78% of all crashes, but that separate analysis should not be treated as a time-stamped replacement for an official current total.

Organize accident records by operation category

Operation category gives you a useful first way to sort U.S. aircraft-accident records. A defining event is an event in an accident sequence used to categorize the accident type, while the aviation segment tells you what kind of operation was involved. The table uses the NTSB’s CY 2018 summary as a dated historical baseline. It presents accidents, fatal accidents, and fatalities separately for each named segment during calendar year 2018.

Operation category CY 2018 accidents CY 2018 fatal accidents and fatalities
Part 121 air carriers 31 accidents 1 fatal accident; 1 fatality
Part 135 commuter and on-demand carriers 42 accidents 7 fatal accidents; 16 fatalities
General aviation 1,275 accidents 224 fatal accidents; 379 fatalities

The Part 121, Part 135, general-aviation, and total figures are all from CY 2018. They cannot be presented as the number of U.S. aircraft accidents in 2026 or as a forecast of present risk.

Use the category as a sorting tool, not as a conclusion about responsibility. A scheduled airline passenger event, a commuter or on-demand operation, and a privately flown general-aviation event may appear in different records and follow different investigative paths. Start with the operation named in the official entry, then identify the defining event, the people affected, the aircraft context, and the stage of the investigation.

The 2018 category figures measure counts, not the complete circumstances of any particular accident. The Part 121 total counts accidents involving that air-carrier segment; the Part 135 total counts commuter and on-demand carriers; the general-aviation total measures its own segment. You should not combine the categories with a separate news list or treat the largest count as an explanation of where a specific passenger was hurt. Match the category to the operation named in the event record before drawing comparisons.

Read a cargo-aircraft record while the investigation is still developing

On September 6, 2026, at about 1:53 p.m. Eastern Daylight Time, the Boeing 767-33A overran runway 30 after landing at Miami International Airport and impacted two ground passenger vehicles. The NTSB described the flight as a domestic cargo operation for Amazon.com Services LLC under 14 CFR Part 121, traveling from San Juan, Puerto Rico, to Miami.

The airplane sustained substantial damage, including a postcrash fire on the right wing. Those details describe reported injuries and damage; they do not identify a legally responsible party or establish why the runway overrun occurred.

The recorder work illustrates how confirmed facts can accumulate before a final conclusion. The NTSB recovered and successfully read out the cockpit voice recorder and flight data recorder at its Vehicle Recorder Laboratory in Washington, DC. The cockpit voice recorder contained more than 2 hours of good-quality audio across four channels, while the flight data recorder contained approximately 54 hours of data and recorded more than 400 parameters. The NTSB said it would convene a group to review the cockpit voice recording and produce a written transcript. Treat that planned review as an investigative step, not as a finding about cause.

Read the Flight 7598 entry in layers:

  1. Identify the date, airport, runway, flight operation, and aircraft.
  2. Separate the reported consequences for crewmembers and people on the ground.
  3. Note the damage description without turning it into a cause conclusion.
  4. Record which investigative materials have already been recovered or read out.
  5. Mark planned work, such as transcript review, as pending activity.

That order keeps a confirmed event detail separate from an investigative task that may produce more information later.

Recorder readouts add documented information while the investigation continues.

Compare general-aviation entries with selected commercial-aircraft records

Selected U.S. aircraft-accident records differ in both operation type and the amount of information available in the cited entry. The comparison below keeps each event’s date, location, aircraft context, and stated investigation status attached to the event rather than combining them into one narrative.

Record Verified occurrence and context Investigation or report status
Piper PA-24 near Bentonville, Arkansas On January 16, 2025, a single-engine Piper PA-24 crashed near Bentonville Municipal Airport after the pilot reported an engine issue. Two people were on board. The FAA said it would investigate.
Glasair II at Gillespie Field, San Diego On January 16, 2025, a Glasair II’s landing gear collapsed while landing at Gillespie Field Airport. Two people were on board. The FAA said it would investigate.
Continental Connection Flight 3407 near Buffalo, New York The Bombardier DHC-8-400 lost control on an instrument approach to Buffalo-Niagara International Airport and crashed into a residence in Clarence Center, about 5 nautical miles northeast of the airport, on February 12, 2009. The NTSB report discusses monitoring, fatigue, training, airspeed and stall procedures, FAA oversight, safety alerts, weather information, and related operational issues.
American Airlines Flight 587 in Belle Harbor, New York On November 12, 2001, the aircraft crashed into a residential area after in-flight separation of the vertical stabilizer and rudder. The NTSB report discusses rudder-system design, rudder-pedal inputs at high airspeeds, aircraft-pilot coupling, maneuvering speed, and upset-recovery training.

The table does not make the general-aviation entries less serious or the commercial-aircraft records more legally decisive. It shows why you should preserve the exact event description and status attached to each authority record.

Follow the record from notification to fact gathering

The investigation path begins with notification and an initial decision about the response. The operator notifies the nearest NTSB office immediately, and the NTSB decides how large a response to make. The NTSB investigates all civil aviation accidents and selected incidents, but not every event receives an on-scene investigative response.

NTSB investigation classes set the depth of an investigation, and the classification can change as safety issues emerge. A significant commercial-transport accident may receive a more extensive response than a limited event handled remotely, but the label is not a ruling on liability. If the classification changes, read the updated authority record instead of relying on the first description you saw.

On-scene fact gathering is different from deciding cause. During that work, the operator preserves wreckage and records, while the NTSB gathers and evaluates information. The NTSB does not determine cause at the scene. That boundary matters after an injury: an early account may identify the location, aircraft, damage, and witnesses without resolving what happened or who may bear legal responsibility.

Label each stage in your notes so a later factual update does not appear to contradict an earlier preliminary description.

Separating response stages helps distinguish fact gathering from conclusions about cause.

Understand what preliminary and final reports can establish

A preliminary report, arriving two weeks to a month after the accident, summarizes factual information and contains no analysis or probable cause. You can use it to check basic details such as the date, location, operation, aircraft, and reported consequences. You should not use its factual synopsis as a final explanation of the accident.

The NTSB may open interview transcripts, laboratory reports, and group factual reports to the public during an investigation or at its end. These materials can add detail to the event record, but each document still needs its own status and date. A media account can help you locate an event, yet the authority record is the place to check whether a detail is preliminary, factual, analyzed, or final.

A final report generally arrives within 12 to 24 months and includes the facts, probable cause, and any safety recommendations. The NTSB investigates to identify probable cause and issue safety recommendations; its investigations do not determine rights, liabilities, or blame. That distinction makes the document type important when you preserve information for a potential claim.

How long a U.S. aircraft-accident investigation usually takes

A U.S. aircraft-accident investigation generally takes 12 to 24 months, but complexity and investigator workload can affect the timing. A preliminary report may arrive in two weeks to a month, while a final report generally takes 12 to 24 months. Those are separate stages: the first summarizes collected facts without analysis or probable cause, and the later report includes facts, probable cause, and safety recommendations.

The FAA entries dated January 16, 2025, show why an initial record may remain brief. The Piper PA-24 entry described a crash near Bentonville Municipal Airport after an engine issue was reported, identified two people on board, and said the FAA would investigate. The Glasair II entry described landing-gear collapse at Gillespie Field Airport in San Diego, identified two people on board, and also said the FAA would investigate. Neither entry should be treated as a completed cause determination.

Use the timeline to decide how you label information, not to delay action that depends on your own injury record. Preserve the dated material you already have, then update it when the responsible authority publishes a new stage of the investigation.

Sort U.S. accident records by operation before comparing them

Sort each entry by operation before comparing it with other records. Mark whether it concerns a Part 121 air carrier, a Part 135 commuter or on-demand carrier, or general aviation. Then use the named authority: the FAA’s accident and incident statement for an FAA-described event, or the NTSB investigation page, report, or factual docket when the NTSB is handling the investigation. Keep the event date, location, aircraft or operation, and publication or update date attached to that category label. For time-sensitive records, record the retrieval date beside the authority’s publication or update date. The publication or update date identifies when the authority issued or updated the record, while the retrieval date identifies when the reader checked it. Recording both dates helps later readers distinguish a newly issued record from an older record reviewed more recently.

Read the record through a category-first set of questions:

  1. Which operation category does the authority entry name: Part 121, Part 135, or general aviation?
  2. What defining event does the entry describe within that category?
  3. Which facts belong to the individual event, and which numbers come from the CY 2018 segment counts?
  4. What investigation stage is identified for that entry?

This keeps historical segment counts separate from the facts and status of a specific accident, and keeps a category label from becoming a conclusion about responsibility.

Historical records show why subject and date both matter. The Flight 801 report focuses on crew performance, approach procedures, training, air traffic control, the inhibited minimum safe altitude warning system, emergency response, oversight, and flight-recorder documentation. Separately, the NTSB summary recorded 31 accidents, 1 fatal accident, and 1 fatality for Part 121 air carriers in CY 2018. The Flight 801 report and the CY 2018 table answer different questions, so you should not use either as a substitute for the authority record of another event.

A compact record card can keep your notes usable:

  • Event name or flight number
  • Date and location
  • Operation category and aircraft
  • Responsible authority
  • Publication or update date
  • Current stage: initial entry, preliminary, factual material, or final report
  • Exact wording for injuries, fatalities, and damage
  • Questions that remain unresolved

Fill in the card from the authority page or report, then add a new dated version when the status changes. Keep media accounts separate from the authority entry so you can tell which detail came from which record.

What documented accident facts may mean for an injury claim

The authority record may help identify the operation, sequence, reported injury, available witnesses, and investigative stage; it does not by itself establish that an airline, crew member, manufacturer, or another party is legally responsible.

Operation type can provide context without answering your individual question. In CY 2018, Part 135 commuter and on-demand carriers recorded 42 accidents, 7 fatal accidents, and 16 fatalities in the cited NTSB summary. That historical category count does not establish what caused a particular injury, whether a legal duty was breached, or whether your facts satisfy any claim requirement.

Preserve medical and incident information after an injury

An aviation injury needs both prompt care and a clear incident record. We recommend reporting your injuries to the airline, seeking medical attention, and documenting the scene and any witnesses after an incident. Seeking medical attention after an airline incident provides important documentation of injuries sustained. If anyone is in immediate danger or has serious or worsening symptoms, contact emergency medical services or the responsible authority promptly; if in doubt, contact a qualified professional promptly.

Use a simple preservation sequence:

  1. Report the injury to the airline and keep the report details with your travel information.
  2. Obtain medical attention and keep the medical records connected to the injury.
  3. Write down what happened while the sequence, location, and witness details are available to you.
  4. Preserve photographs, witness information, and other incident details you already possess.
  5. Keep the authority entry and later updates with the medical information rather than relying on memory alone.

Certain medical records are needed for aviation-injury cases. Keep them in their original form and add later records as treatment continues.

Do not treat an early factual synopsis as a probable-cause finding, and do not wait for a final report before asking what options may exist. Preserve the information within your control and label uncertainty instead of filling gaps with an assumed cause.

Know when prompt qualified aviation-injury help may be appropriate

Prompt qualified aviation-injury help may be appropriate when you or a family member suffered an injury or loss, when the event involves an airline or crew issue, or when the authority record is developing and the available information is difficult to organize. We recommend reaching out to aviation-lawyers who can assist with the complexities of the claims process and ensure requests are submitted promptly. Passengers experiencing airline negligence may seek legal action to understand their rights and pursue justice, while the facts and applicable law determine what questions require review.

A reporting rule can also explain why an authority may become involved without answering a claim question. For large multi-engine aircraft weighing more than 12,500 pounds maximum certificated takeoff weight, certain inflight electrical-system failures requiring sustained emergency-bus use are among the FAA’s listed occurrences requiring notification. That threshold and condition describe a reporting requirement; they do not decide your eligibility, liability, damages, or legal deadline.

You do not need to know the final cause before organizing a qualified review. Bring the dated authority entry, medical information, witness details, and any account of what happened. A family may ask about options while the investigation continues, and prompt aviation-law assistance can help keep the developing record and the injury information connected.

Use the situation to choose the immediate direction:

  • If you were injured, keep the airline report, medical information, and incident details together, then seek prompt qualified review.
  • If a family member died or suffered a serious injury, preserve the authority record and ask about available options without waiting for the final report.
  • If the record is incomplete or changing, label the unresolved points and bring each dated update to the review.

The action is the same in each branch: preserve what you have and seek qualified aviation-law help when the injury, loss, or developing investigation makes the next question difficult to assess.

Bring the accident and injury record to the next review

A useful next step is to assemble the authority record, the date and operation category, medical information, witness details, and preserved incident facts in one place. A qualified professional decides individual suitability and legal options from the facts, applicable law, and jurisdiction. You can begin with the information already available and update it as the investigation develops.


Questions about verifying U.S. aircraft-accident records

How many U.S. aircraft accidents occurred in 2026?

A current, authoritative nationwide total for 2026 must be tied to a defined date range in FAA and NTSB records. Do not treat the CY 2018 figures as a 2026 count. For a current total, check the relevant FAA and NTSB records for a defined date range and keep accidents, fatal accidents, and fatalities in separate categories.

Can an early aircraft-accident report prove who was at fault?

No. A preliminary report summarizes collected facts without analysis or probable cause, and an NTSB investigation identifies probable cause and safety recommendations rather than deciding rights, liability, or blame. Treat early descriptions as developing information and have a qualified professional assess how the available facts may relate to an individual claim.

What information should I preserve after an aircraft injury?

Report the injury to the airline, seek medical attention, and keep the related medical records. Also preserve photographs, witness details, travel information, the airline report, your account of what happened, and dated FAA or NTSB updates. Keeping the original wording and dates helps separate your experience from later assumptions about cause or responsibility.

How long does a U.S. aircraft-accident investigation usually take?

A preliminary report may arrive in about two weeks to a month. A final report generally takes 12 to 24 months, although complexity and investigator workload can change the timing. You do not need to wait for the final report to preserve injury information or ask about possible options.


Were you hurt on a flight?Tell us what happened. The consultation is free.
Free case evaluation