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.
1990 Mooney M20J 201
N201SE · Serial 24-1706-14
Currently Registered as of Oct 14, 2026Manufacturer-certified specifications for this aircraft type — not a claim about this specific airframe's current configuration.
N-Number History
- N201SE — Sep 9, 2026 to present
Full FAA Registration Record
| Serial Number (as registered) | 24-1706-14 |
|---|---|
| Aircraft Unique ID Number | 00755091 |
| FAA Manufacturer / Model Code | 5870219 |
| Aircraft Engine Type | Reciprocating |
| Engine Manufacturer / Model | LYCOMING I0360 SER A&C |
| Certification of Aircraft Registration Date | Dec 4, 2023 |
| Airworthiness Certificate Issue Date | Dec 10, 1990 |
| Airworthiness Classification | Standard (Normal) |
| Registration Status | Currently Registered |
| Aircraft Registration Expiration Date | Dec 31, 2030 |
| Last FAA Update | Oct 14, 2026 |
| Registration Country | US |
| Registration State | TX |
| Weight Class | CLASS 1 |
| TC Data Sheet | — |
| TC Data Holder | — |
| FAA AIDS Reports | 20170128000599I, 20001026038619A, 19900610019849A, 19840415021039I, 19790520026239I |
Accident & Incident History (NTSB)
-
Accident
Oct 26, 2000 — DELAND, FL
NTSB event number MIA01LA018 — view NTSB's investigation summary for what NTSB found.
-
Accident
Jun 11, 1990 — ANDREWS, NC (possible match)
NTSB event number 20001212X23318
See NTSB history for every Mooney M20J 201 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.
-
LINE
Jan 27, 1998 (possible match)
THE PILOT REPORTED A ROUGH ENGINE THAT RESULTED IN A PRECAUTIONARY LANDING. THE INITIAL INSPECTION REVEALED THE NR 1 CYLINDER FUEL INJECTOR LINE WAS BROKEN IN TWO AT THE NOZZLE END. THE FLIGHT SCHOOL OPERATES A FLEET OF 8 M20J AIRCRAFT. AD 93-02-05 IS ALWAYS C/W AT EACH 100-HOUR INSPECTION. THIS IS A COMMON FAILURE, AND VERY DANGEROUS.
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.
-
Incident
Jan 28, 2017 — FORT WORTH, TX (possible match)
General Information
- N-Number (as reported)
- 201SE
- Event Time
- 16:01
- Airport
- FORT WORTH SPINKS
- Mid Air Collision
- Not A Midair
- Flight Phase
- Landing: Touchdown
Aircraft Information
- Damage
- Minor
- Aircraft (as reported)
- MOONEY M20J
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- LYCOMING I0360 SER A&C
- Operator
- —
- Total Aboard
- 2
- Injuries
- 0 fatal, 0 non-fatal
Pilot In Command
- PIC Flight Time Total Hours
- 3,000
- PIC Flight Time Total Make/Model Hours
- 4
- PIC Flight Time Hours (Last 90 Days)
- 100
Event Remarks
PILOT 2 STATED HE WAS PRACTICING COMMERCIAL MANEUVERS AND HAD BEEN DOING TOUCH AND GOS. ADVISED TOWER THIS WOULD BE FULL STOP. PILOT 2 STATED HE JUST FORGOT TO PUT THE GEAR DOWN. PILOT 2 WAS RECEIVING COMMERCIAL INSTRUCTION FROM PILOT 1
FAA AIDS report 20170128000599I
-
Accident
Oct 26, 2000 — DELAND, FL (possible match)
General Information
- N-Number (as reported)
- 201SE
- Event Time
- 12:45
- Airport
- DELAND MUNI-SIDNEY H TAYLOR
- Mid Air Collision
- Not A Midair
- Flight Phase
- Roll-Out (Fixed Wing)
Aircraft Information
- Damage
- Substantial
- Aircraft (as reported)
- MOONEY M20J
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- —
- Operator
- —
- Total Aboard
- 2
- Injuries
- 0 fatal, 0 non-fatal
Pilot In Command
- PIC Flight Time Total Hours
- 685
- PIC Flight Time Total Make/Model Hours
- 29
- PIC Flight Time Hours (Last 90 Days)
- 225
Event Remarks
(-23) A/C ALNDED RUNWAY 5 DELAND MUNICIPAL AIRPORT. AFTER TOUCHDOWN PILOT LOST CONTROL OF A/C AND SWERVED ACROSS RUNWAY CENTER LINE SEVERAL TIMES EXITING SOUTH SIDE OF RUNWAY. AFTER STRIKING A RUNWAY MARKER SIGN WITH THE RIGHT WING THE AIRCRAFT RETURNED TO THE RUNWAY AND TAXIED TO THE RAMP. A LARGE HOLE WAS PUNCTURED IN THE BOTTOM OF THE RIGHT WING JUST OUTBD OF THE FUEL TANK, ONE STRINGER WAS BROKEN AND ONE RIB WAS DAMAGED. THE AILERON PUSH PULLTUBE WAS BENT. THE RIGHT FLAP SUSTAINED MINOR DAMAGE. (.4) ON OCTOBER 26, ABOUT 1245 EASTERN DAYLIGHT TIME, AND MOONEY, M-20J, N201SE, REGISTERED TO A PRIVATE INDIVIDUAL, AND OPERATED BY EMBRY-RIDDLE AERONAUTICAL UNIVERSITY, AS A TITLE 14 CFR PART 91 INSTRUCTIONAL FLIGHT, COLLIDED WITH A RUNWAY SIGN DURING THE LANDING ROLLOUT AT DELAND, FLORIDA. VISUAL METEOROLOGICAL CONDITIONS PREVAILED, AND NO FLIGHT PLAN WAS FILED. THE AIRCRAFT INCURRED SUBSTANTIAL DAMAGE. THE COMMERCIAL-RATED FLIGHT INSTRUCTOR, AND DUAL STUDENT WERE NOT INJURED. THE FLIGHT ORIGINATED FROM DELAND, FLORIDA, THE SAME DAY, ABOUT 1200. THE FLIGHT INSTRUCTOR STATED THAT HE WAS PROVIDING INSTRUCTION TO A PRIVATE-RATED PILOT SEEKING A COMMERCIAL CERTIFICATE . THE INSTRUCTOR FURTHER STATED THAT THE STUDENT HAD JUST MADE AN EXCELLENT LANDING, BUT DURING THE LANDING ROLLOUT HE APPLIED VIOLENT PRESSURE TO THE RIGHT BRAKE, WHICH MOVED THE NOSE ABOUT 70 DEGREES TO THE RIGHT, IN A SKID TOWARD THE RIGHT SIDE OF THE RUNWAY. THE INSTRUCTOR SAID THAT HE IMMEDIATELY TOOK CONTROL OF THE AIRPLANE FROM THE STUDENT, BUT THE STUDENT MAINTAINED HIS FEET ON THE BRAKES, AND THE AIRPLANE COLLIDED WITH A RUNWAY SIGN, INCURRING SUBSTANTIAL DAMAGE. THE STUDENT STATED THAT THE TOUCHDOWN WAS SMOOTH, AND THE ROLLOUT WAS ON THE CENTERLINE OF THE RUNWAY. THE STUDENT FURTHER STATED THAT HE APPLIED THE BRAKES, AND IT LOOKED TO HIM AS IF THE LEFT BRAKE DIDN'T SEEM TO TAKE EFFECT. THE STUDENT STATED THAT IT IS POSSIBLE THAT HE COULD HAVE BEEN JUST USING THE RIGHT BRAKE TO STOP THE AIRCRAFT, AND UPON APPLICATION OF THE BRAKES THE AIRCRAFT STARTED SKIDDING. THE STUDENT SAID HE THEN TRANSFERRED CONTROLS TO THE INSTRUCTOR, BUT THE AIRPLANE WAS TRAVELING TOO FAST, AND IT WENT INTO THE GRASS, AND ONE WING COLLIDED WITH A RUNWAY SIGN. UNDER THE SUPERVISION OF AN FAA INSPECTOR, THE OPERATOR CONDUCTED A POSTACCIDENT EXAMINATION OF THE AIRCRAFT, AND A FUNCTIONAL CHECK OF THE BRAKES ON BOTH THE LEFT AND RIGHT PILOT POSITIONS, AS WELL AS REMOVED AND CHECKED BOTH THE LEFT AND RIGHT MAIN LANDING GEAR BRAKE PADS. THE EXAMINATION DID NOT REVEAL ANY PREEXISTING MALFUNCTIONS TO THE AIRCRAFT, OR ITS SYSTEMS. IN ADDITION, A FERRY PERMIT WAS OBTAINED, AND THE AIRCRAFT WAS FERRIED TO AN INDEPENDENT AUTHORIZED MOONEY SERVICE CENTER, WHERE AN EVALUATION WAS CONDUCTED ON THE STEERING AND BRAKE SYSTEMS, AND NO ABNORMALITIES WERE OBSERVED.
FAA AIDS report 20001026038619A
-
Accident
Jun 10, 1990 — ANDREWS, NC (possible match)
General Information
- N-Number (as reported)
- 201SE
- Event Time
- 22:45
- Airport
- ANDREWS-MURPHY ARPT
- Mid Air Collision
- Not A Midair
- Flight Phase
- Unauth Low Level Opns
Aircraft Information
- Damage
- Destroyed
- Aircraft (as reported)
- MOONEY M20J
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- LYC IO360A1A
- Operator
- —
- Total Aboard
- 2
- Injuries
- 2 fatal, 0 non-fatal
Pilot In Command
- PIC Flight Time Total Hours
- 1,064
- PIC Flight Time Total Make/Model Hours
- 585
- PIC Flight Time Hours (Last 90 Days)
- 8
Event Remarks
FLEW INTO SIDE OF MOUNTAIN ON CLIMBOUT FROM AIRPORT. NO GROUND LIGHTS.
FAA AIDS report 19900610019849A
-
Incident
Apr 15, 1984 — AMERICUS, GA (possible match)
General Information
- N-Number (as reported)
- 201SE
- Event Time
- 19:00
- Airport
- AMERICUS
- Mid Air Collision
- Not A Midair
- Flight Phase
- Roll-Out (Fixed Wing)
Aircraft Information
- Damage
- Minor
- Aircraft (as reported)
- MOONEY M20J
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- LYC IO360A3B6
- Operator
- —
- Total Aboard
- 1
- Injuries
- 0 fatal, 0 non-fatal
Pilot In Command
- PIC Flight Time Total Hours
- 605
- PIC Flight Time Total Make/Model Hours
- 388
- PIC Flight Time Hours (Last 90 Days)
- 37
Event Remarks
LANDING GEAR COLLAPSED AS NOSE WHEEL TOUCHED ON THE ROLLOUT. ACTUATOR ROD HOUSING ATTACHED TO GEAR MOTOR FAILED.
FAA AIDS report 19840415021039I
-
Incident
May 20, 1979 — BENTON HARBOR, MI (possible match)
General Information
- N-Number (as reported)
- 201SE
- Event Time
- 11:10
- Airport
- ROSS
- Mid Air Collision
- Not A Midair
- Flight Phase
- Roll-Out (Fixed Wing)
Aircraft Information
- Damage
- Minor
- Aircraft (as reported)
- MOONEY M20J
- Flight Conducted Under
- GENERAL OPERATING RULES
- Engine (as reported)
- —
- Operator
- —
- Total Aboard
- —
- Injuries
- 0 fatal, 0 non-fatal
Pilot In Command
- PIC Flight Time Total Hours
- 1,017
- PIC Flight Time Total Make/Model Hours
- 650
- PIC Flight Time Hours (Last 90 Days)
- 0
Event Remarks
PILOT INADVERTENTLY RETRACTED GEAR ON ROLLOUT.
FAA AIDS report 19790520026239I
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.
