You hear about a small plane going down in the news. Maybe a friend mentions a corporate jet incident near a regional airport. Your first instinct? Find the report.

But where does it actually live, and who writes it? FAA crash reports aren't always what people think they are. Once you understand the split between the FAA and the NTSB, the whole system starts making sense.

This guide walks you through where the reports come from, what's inside them, and how to pull records yourself. Whether you're prepping for a checkride or just curious about a local accident, the records are out there. Mostly free. Mostly public. You just need to know the map.

Aviation safety in the United States runs on a strange but effective two-agency model. The Federal Aviation Administration regulates. The National Transportation Safety Board investigates. They share data, they coordinate, but their reports look very different.

Knowing which one you want will save you hours of clicking through the wrong databases. The pages that follow lay out exactly where each type of record lives, what's inside it, who you talk to when you need more, and how to read the documents like a working safety professional rather than a casual reader.

Let's clear up the biggest source of confusion first. The FAA does not write the headline crash report you see quoted in news stories. That's the NTSB's job.

The National Transportation Safety Board is an independent federal agency. It doesn't enforce rules, it doesn't certify pilots, and it doesn't grant operating certificates. It investigates. When something falls out of the sky, NTSB investigators show up, gather evidence, pull flight data, and eventually publish a probable cause finding. That document is the gold standard.

The FAA's role is different. It writes the rules, certifies aircraft and pilots, runs the air traffic control system, and enforces compliance. When an accident happens, the FAA participates as a party — providing technical expertise on certification, operations, and ATC.

But it doesn't issue the official cause determination. The FAA does, however, maintain its own incident databases for regulatory purposes. That's where the confusion creeps in. You might find an event in both an NTSB report and an FAA database, with different details and different angles.

One more wrinkle worth knowing. The NTSB is small. It has roughly 400 staff covering aviation, rail, highway, marine, and pipeline accidents combined. That means in most general aviation crashes the NTSB delegates the on-scene work to a single investigator-in-charge, who pulls in FAA inspectors, manufacturer reps, and operator personnel as parties.

Every party signs an agreement to share information but not to speak publicly until the report is final. So if you see a manufacturer making statements during the investigation, that's a violation of the party process, and it tells you something about how that company handles accountability. Reading reports gives you that context too.

So where are these reports actually hosted? The NTSB Aviation Accident Database is the starting point for most searches. You'll find it at ntsb.gov, and it covers civil aviation accidents from 1962 forward.

The database is searchable by date, location, aircraft make and model, registration number, severity, and a dozen other fields. Each entry links to the full narrative report, factual findings, probable cause, and supporting documents — photos, weather data, ATC transcripts, maintenance records.

For events after roughly 2008, you'll typically get a complete docket with hundreds of pages of attached materials. Older reports tend to be shorter — more summary-style — but still useful for research.

The FAA maintains the Accident & Incident Data System, usually called AIDS. This database leans toward incidents that didn't meet the NTSB's accident threshold. Think runway excursions without injury, minor mechanical failures, or air traffic deviations.

AIDS data is rougher than NTSB narratives. Fewer pages. More codes. But for trend analysis or operational research, it fills the gaps the NTSB doesn't cover.

Beyond those two, there are several supporting databases worth knowing about. The FAA's Service Difficulty Reporting system logs maintenance issues reported by mechanics and operators. The FAA Accident/Incident Preliminary Data archive holds initial notification reports filed within 24 hours of an event.

The CAROL Query tool on the NTSB site lets you search across multiple modes at once, useful if you're researching accidents that crossed boundaries — a helicopter that went down while supporting a marine operation, for instance.

And for international context, the ICAO Accident/Incident Data Reporting System collects similar records from member states worldwide. Most U.S. researchers stick with NTSB and AIDS for domestic work, but cross-referencing the international database can reveal patterns specific to certain aircraft types or operations.

The Aviation Safety Reporting System — ASRS — deserves its own paragraph. It's run by NASA, of all places, on behalf of the FAA.

The idea was simple but radical when it launched in the 1970s. Give pilots, controllers, and crew a way to report mistakes, near misses, and hazards without getting punished. If you file an ASRS report within ten days of an incident, you generally get immunity from FAA enforcement action on most violations.

In exchange, the system collects an enormous library of close calls — the stuff that almost became a crash report but didn't. ASRS data is searchable at asrs.arc.nasa.gov. The reports are stripped of identifying details.

You'll never see a registration number or a specific pilot's name. What you get instead is the narrative — the pilot's own words about what went wrong, what they noticed, what they'd do differently.

For student pilots, this is incredibly powerful study material. You're reading firsthand accounts of altitude busts, runway incursions, fuel mismanagement, and weather decisions gone sideways. It's the closest you can get to learning from mistakes you haven't made yet.

ASRS also publishes a monthly newsletter called CALLBACK, themed around specific hazards — wake turbulence, fatigue, automation surprises. The back issues are free and downloadable. Worth subscribing if you fly regularly.

What does a finished NTSB report actually contain? At the top, you'll find the basics — date, time, location, aircraft type, registration, operator, and a one-line severity classification.

Then comes the factual narrative. This section is dry on purpose. It describes the flight, the conditions, and what was found at the scene. No interpretation, just the evidence.

After that, the analysis section. Here investigators connect the dots — explaining why the engine quit, why the pilot got disoriented, why the approach went wrong. The probable cause statement follows. It's usually one to three sentences, and it's the most-quoted part of any report.

Major accidents get safety recommendations attached. These are the NTSB's most powerful tool. They can't write regulations, but they can publicly call on the FAA, manufacturers, or operators to change something.

The FAA either accepts, rejects, or partially implements each recommendation, and the back-and-forth is itself public record. Over decades, this dialogue has produced everything from terrain awareness warning systems to mandatory upset training to redesigned cockpit displays.

Reading the recommendation history of any major accident is a master class in how aviation slowly gets safer. Smaller GA reports usually skip the recommendation section entirely. They're shorter, more focused, and often follow a template — pilot, aircraft, weather, sequence, cause.

But even the shortest report carries the same structure underneath. Once you've read ten or twelve of them, the format becomes second nature, and you can skim a new report in five minutes and pull the lesson out cleanly.

Sometimes the public database doesn't have what you need. Maybe you want a specific document from a docket that isn't online. Maybe you're researching an older accident that predates digital records.

That's where the Freedom of Information Act comes in. Both the FAA and the NTSB process FOIA requests, and aviation records are among the most-requested categories. You submit the request in writing — either through the agency's online portal or by mail — describing the records you want.

Be specific. Vague requests get bounced or take forever. FOIA responses typically arrive within 20 working days, though complex requests can stretch much longer.

Some records carry fees if the request is large or commercial in nature, but personal and educational requests are usually free or low-cost. You can request pilot records, aircraft maintenance histories, enforcement actions, certification documents, and ATC recordings.

The FAA's FOIA office at foia.faa.gov has a searchable library of frequently-requested records — start there before filing your own request. You might find what you need already published.

A few exemptions to know. Medical certification records are protected under the Privacy Act and require either the airman's consent or evidence of their death. Ongoing enforcement actions can be withheld until resolved. Security-sensitive information, like detailed airport vulnerability assessments, is exempt under separate rules.

For everything else, the default posture is disclosure. If your request is denied, you have the right to appeal in writing, and a surprising number of appeals succeed. The system is built to lean toward openness — you just have to ask correctly.

Now the part nobody mentions in pilot training but every good instructor pushes. Read accident reports. Read them weekly. Read them when you're bored. Read them before a long cross-country.

There's a reason flight schools assign them, and it's not because instructors enjoy grim stories. It's because the same accident categories keep repeating, decade after decade, and reading the reports rewires your decision-making.

You start recognizing the setup before you're in it. You catch the warning signs because you've seen them written up dozens of times. Some categories show up so often they have their own acronyms.

CFIT — controlled flight into terrain — is when a perfectly functional aircraft is flown into the ground, usually because of poor situational awareness, weather, or distraction. Stall/spin accidents tend to happen in the traffic pattern, often during base-to-final turns with too much rudder and not enough airspeed.

Weather-related accidents — VFR into IMC, thunderstorm penetration, icing — make up a stubborn share of fatalities year after year. Fuel mismanagement still puts planes down, even with modern fuel totalizers. Reading the reports doesn't make you immune. But it makes you less likely to be next.

The AOPA Air Safety Institute publishes annual Nall Reports that aggregate this data and break it down by accident type, flight phase, and contributing factor. Free downloads. Pair them with the raw NTSB reports and you've got a complete picture of where the danger actually sits.

For student pilots, accident reports map onto the FAA written exam more directly than you might expect. ADM — aeronautical decision-making — is a huge slice of the knowledge test, and the FAA's textbook examples are pulled straight from real accidents.

The Pilot's Handbook of Aeronautical Knowledge dedicates entire chapters to risk management frameworks built around recurring accident causes. When you study PAVE, IMSAFE, or the 5P checklist, you're studying tools developed because investigators kept seeing the same human factors fail in the same ways.

Connecting the abstract checklist to a real report makes it stick. If you're an instructor, accident reports give you teaching material that no textbook can match.

Show a student the probable cause for a stall-spin on base-to-final. Then sit in the airplane and demonstrate the setup — too tight a pattern, overshooting the runway centerline, the temptation to skid the turn.

The lesson lands differently when there's a name and a date behind the technique. The NTSB even publishes monthly safety alerts and a regularly updated Most Wanted List of transportation safety improvements, which makes excellent classroom material.

Pair the Most Wanted List with the FAA's Compliance Program documents and you can see exactly where the regulator is focused this year. Together they're a roadmap for the next decade of certificate action, advisory circulars, and equipment mandates. If you're studying for an instructor rating or a commercial checkride, the oral examiner often pulls questions from this material.

A few practical tips before you go diving in. The NTSB database uses a slightly idiosyncratic search interface. If your search returns nothing, try broader date ranges and partial location names.

The system also distinguishes between accidents and incidents, so make sure your filter matches what you're looking for. For aircraft-specific research, the make/model search is your friend.

Pulling every accident involving a Cessna 172 or a Cirrus SR22 gives you patterns specific to that airframe. Looking at one type? You'll see the same scenarios appear over and over, which is exactly what makes the data so educational.

For FOIA requests, write like a librarian, not a lawyer. Describe the records by date, location, aircraft, registration, and event if you have them. Include the case or accident number when possible — both NTSB and FAA assign unique identifiers, and quoting them speeds things up dramatically.

If you don't know the number, search the public database first and pull it from there. Finally, remember the bigger picture. These reports exist because hundreds of people died so the rest of us could learn. Treat them with the weight they deserve.

Read them, learn from them, and let them sharpen your judgment every time you preflight an airplane. The probable cause for the next crash isn't fate. It's almost always written somewhere in an old report you could have read first.

One last suggestion. Build a habit. Bookmark the NTSB and ASRS sites, subscribe to the AOPA Air Safety newsletter, and set a recurring reminder to read at least one full report each month. Pick reports that match your kind of flying — same airplane class, same mission profile, same weather conditions you typically launch into.

Over a year, that's twelve detailed case studies. Over a flying career, that's hundreds. Few things sharpen judgment faster than seeing how skilled, current, well-equipped pilots got into trouble and what the gap was between their plan and their actual flight. That gap is where you live every time you fly. Closing it, even a little, is what the reports are for.