Aircraft Research
Look up any FAA-registered aircraft by N-number or serial number, browse aggregate safety and maintenance records by year, manufacturer, and model, or search the registry for aircraft matching specific safety criteria — all free, no account needed.
Search for Full FAA Registration and Aircraft Details Record Look up one specific aircraft by N-number or serial number — full FAA registration and airworthiness details, N-number history, and its accident/service-difficulty history.
1974 Piper Navajo
N200RA · Serial 31P7400198
Currently Registered as of Oct 16, 2026Manufacturer-certified specifications for this aircraft type — not a claim about this specific airframe's current configuration.
N-Number History
- N200RA — Sep 9, 2026 to present
Full FAA Registration Record
| Serial Number (as registered) | 31P7400198 |
|---|---|
| Aircraft Unique ID Number | 00392902 |
| FAA Manufacturer / Model Code | 7103120 |
| Aircraft Engine Type | Reciprocating |
| Engine Manufacturer / Model | LYCOMING TI0-541 SER |
| Certification of Aircraft Registration Date | Jun 3, 1996 |
| Airworthiness Certificate Issue Date | Jun 7, 1996 |
| Airworthiness Classification | Standard (Normal) |
| Registration Status | Currently Registered |
| Aircraft Registration Expiration Date | Jan 31, 2028 |
| Last FAA Update | Oct 16, 2026 |
| Registration Country | US |
| Registration State | MO |
| Weight Class | CLASS 1 |
| TC Data Sheet | — |
| TC Data Holder | — |
| FAA AIDS Reports | 20230720017039A, 20000406014799I |
Accident & Incident History (NTSB)
-
Accident
Jul 20, 2023 — Kearney, MO
Probable cause: Aircraft-Aircraft handling/service-Maintenance/inspections-(general)-Inadequate inspection; Aircraft-Aircraft power plant-Engine (reciprocating)-(general)-Incorrect service/maintenance; Aircraft-Aircraft power plant-Engine fuel and control-Fuel injector nozzle-Fatigue/wear/corrosion; Aircraft-Aircraft oper/perf/capability-Performance/control parameters-Powerplant parameters-Not attained/maintained; Personnel issues-Action/decision-Action-Incorrect action performance-Pilot; Personnel issues-Task performance-Maintenance-(general)-Maintenance personnel
NTSB event number CEN23FA314 — view NTSB's investigation summary for what NTSB found.
See NTSB history for every Piper Navajo on file → (FAA-registered and foreign/military aircraft, combined)
Service Difficulty Reports (FAA)
Filing a Service Difficulty Report is required by law for repair stations, aircraft manufacturers, and airlines, but is largely voluntary for privately owned, individually operated aircraft. A blank result below reflects who's required to report a defect, not necessarily a clean maintenance history — and conversely, reports on file are rarely the complete picture for an aircraft that's mostly been privately maintained.
No FAA Service Difficulty Reports found for this aircraft.
Reported Incidents (FAA AIDS)
The FAA's Accident/Incident Data System tracks events below the damage/injury threshold that makes something an NTSB-investigated accident — mostly minor incidents that never became a full NTSB case. A report below marked "Accident" may be the same event already shown above under NTSB; that overlap is expected, not a data error.
-
Accident
Jul 20, 2023 — EXCELSIOR SPRIN, MO (possible match)
General Information
- N-Number (as reported)
- 200RA
- Event Time
- 09:39
- Airport
- MIDWEST NATIONAL AIR CENTER
- Mid Air Collision
- Not A Midair
- Flight Phase
- Takeoff: Climb Out
Aircraft Information
- Damage
- Destroyed
- Aircraft (as reported)
- PIPER PA-31P
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- LYCOMING TI0-541 SER
- Operator
- —
- Total Aboard
- 1
- Injuries
- 1 fatal, 0 non-fatal
Event Remarks
PILOT TOOK OFF ON A FERRY FLIGHT TO RELOCATE THE AIRCRAFT TO KINGMAN AIRPORT/CLYDE CESSNA FIELD(9K8) KINGMAN, KANSAS TO COMPLETE AN OVERDUE ANNUAL INSPECTION. DURING TAKEOFF AND ROTATION, WITNESSES STATED THE AIRCRAFT SEEMED TO BE OPERATING AT LESS THAN FULL POWER AND PULLED TO THE RIGHT ONCE THE AIRCRAFT ROTATED AND TOOK FLIGHT. WITNESSES FURTHER STATED THE AIRCRAFT STRUGGLED TO GAIN ALTITUDE TO CLEAR THE TREE LINE NORTH OF THE RUNWAY. AFTER RETRACTION OF THE LANDING GEAR, THE AIRCRAFT BEGAN TO SLOWLY GAIN ALTITUDE AND ONCE CLEAR OF THE TREES, THE AIRCRAFT MADE A LEFT TURN (WEST) OUT OF SIGHT OF THE WITNESSES. THE AIRCRAFT, STILL STRUGGLING TO GAIN AND MAINTAIN ALTITUDE, IMPACTED HIGH TENSION POWER LINE GUY WIRES AND THE RIGHT WING THEN CLIPPED A TREE APPROXIMATELY 30 FEET ABOVE THE GROUND. THE AIRCRAFT THEN LANDED IN A BEAN FIELD WITH THE GEAR RETRACTED AND SLID ALONG THE GROUND APPROXIMATELY 400 FEET BEFORE COMING TO A STOP WHERE IT VERY QUICKLY BURST INTO FLAMES CAUSING THE DESTRUCTION OF THE AIRCRAFT.
FAA AIDS report 20230720017039A
-
Incident
Apr 6, 2000 — OLATHE, KS (possible match)
General Information
- N-Number (as reported)
- 200RA
- Event Time
- 08:55
- Airport
- JOHNSON COUNTY EXECUTIVE ARPT
- Mid Air Collision
- Not A Midair
- Flight Phase
- Normal Cruise
Aircraft Information
- Damage
- —
- Aircraft (as reported)
- PIPER PA31P
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- LYC TIO541*
- Operator
- —
- Total Aboard
- 1
- Injuries
- 0 fatal, 0 non-fatal
Pilot In Command
- PIC Flight Time Total Hours
- 1,200
- PIC Flight Time Total Make/Model Hours
- 300
- PIC Flight Time Hours (Last 90 Days)
- 5
Event Remarks
(-23) AIRCRAFT DECLARED AN EMERGENCY AND DIVERTED TO JOHNSON COUNTY EXECUTIVE AIRPORT (OJC), DUE TO RIGHT ENGINE SMOKING. AIRCRAFT LANDED WITHOUT INCIDENT. EMERGENCY EQUIPMENT ON STANDBY. THE SMOKE WAS CAUSED BY AN OIL LEAK. NO DAMAGE TO THE AIRCRAFT OR INJURY TO PILOT.
FAA AIDS report 20000406014799I
Registration data, N-number history, and manufacturer type specs come from the FAA. Accident/incident history comes from the NTSB, matched by N-number (older records are cross-checked against this aircraft's registration history where possible — see the "possible match" note above for the residual cases we can't fully confirm). Service difficulty reports come from the FAA's own SDR program. Reported incidents come from the FAA's Accident/Incident Data System (AIDS), matched by N-number. None of this is a substitute for reviewing an aircraft's logbooks and maintenance records before purchase.
Search for Safety and Maintenance Records by Year, Make and Model of Aircraft See aggregate NTSB accident/incident history, FAA Service Difficulty Reports and FAA Accident/Incident Data System Reports across every aircraft of a given year, manufacturer, and/or model — not just one airframe.
Pick at least a Year or a Manufacturer to get started.
Pick a Year or Manufacturer above to see its safety and maintenance record.
Search for Aircraft by Safety History Search the whole registry at once for year/manufacturer/model combinations that match specific safety and maintenance criteria you choose.
Find every year/manufacturer/model combination matching the safety and maintenance criteria below — pick at least one filter to search on.
Search for Deregistered and Out-of-Service Aircraft List the individual aircraft of a given year, manufacturer, and/or model that FAA no longer lists as an active (Valid) registration, along with N-number and whatever FAA registration status and NTSB accident history we have on record for each.
Optionally narrow by Year, Manufacturer, Model, and/or NTSB Accident History or FAA AIDS History below — leave everything at "All"/"Any" to browse every deregistered or out-of-service aircraft on file.
FAA's own deregistration data doesn't include a reason code (no "sold," "destroyed," or "scrapped" field), and its Registration Status values (shown in the results below) run almost entirely "Unknown" in practice — not a useful way to narrow this list. NTSB Accident History instead filters by whether that specific airframe has an NTSB accident or incident on record, and whether any of them marked it Destroyed — the closest signal this report can offer for whether an aircraft's exit from the registry followed an accident. FAA AIDS History filters the same way using FAA's own Accident/Incident Data System records instead, matched by that airframe's event type (Incident/Accident) and reported damage.
Loading…
Frequently Asked Questions
What's the difference between an NTSB report and an FAA AIDS report?
The NTSB investigates accidents and serious incidents — events that meet a specific federal damage or injury threshold. FAA's Accident/Incident Data System (AIDS) tracks events that fall below that threshold: mostly minor incidents that were reported to the FAA but never rose to the level of a full NTSB investigation. Because both systems can end up recording the same real-world event, a report marked "Accident" under FAA AIDS may be the very same event already shown above under NTSB — that overlap is expected, not a data error.
What does "(possible match)" mean next to a report?
Every NTSB, FAA Service Difficulty, and FAA AIDS record is linked to a specific aircraft by its N-number (and, when available, its manufacturer serial number). A record is marked "confirmed" when our own tracked registration history shows this exact airframe held that N-number on the date of the event. It's marked "(possible match)" when we can't fully verify that — most often because the event happened further back than our registration history reaches. N-numbers get reassigned to a completely different aircraft over the decades, so a "possible match" is our best available inference, not a certainty.
My aircraft shows no FAA Service Difficulty Reports (SDRs) — does that mean it has a clean maintenance history?
Not necessarily. Filing a Service Difficulty Report is required by law for repair stations, aircraft manufacturers, and airlines, but it's largely voluntary for privately owned, individually operated aircraft. A blank SDR result reflects who's required to report a defect, not necessarily a clean maintenance history.
My aircraft shows no NTSB or FAA AIDS records — is that unusual?
No — it's the common case. The large majority of aircraft never appear in either system at all. An empty result under Accident & Incident History (NTSB) or Reported Incidents (FAA AIDS) simply means no event of that kind is on file for this airframe; it isn't a sign that data is missing.
Does a clean record on this page mean the aircraft is safe to buy?
No. This page reflects only what's on file in federal public records — it isn't a substitute for reviewing an aircraft's own logbooks and maintenance records, and ideally having a qualified mechanic perform a pre-purchase inspection, before you buy.
Where does this data come from, and how current is it?
Registration data, N-number history, and manufacturer type specs come from the FAA's own registry. Accident and incident history comes from the NTSB. Service difficulty reports come from the FAA's SDR program. Reported incidents come from the FAA's Accident/Incident Data System (AIDS). All four are public federal records that we import and refresh on an ongoing basis, so newly filed reports appear over time — but there's typically some lag between when the FAA or NTSB publishes a record and when it shows up here.
