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.
2016 Embraer ERJ 170-200 LR
N200SY · Serial 17000623
Currently Registered as of Oct 6, 2026Manufacturer-certified specifications for this aircraft type — not a claim about this specific airframe's current configuration.
N-Number History
- N200SY — Sep 9, 2026 to present
Full FAA Registration Record
| Serial Number (as registered) | 17000623 |
|---|---|
| Aircraft Unique ID Number | 01238215 |
| FAA Manufacturer / Model Code | 3260415 |
| Aircraft Engine Type | Turbofan |
| Engine Manufacturer / Model | GE CF34-8E5 |
| Certification of Aircraft Registration Date | Dec 15, 2016 |
| Airworthiness Certificate Issue Date | Dec 16, 2016 |
| Airworthiness Classification | Standard (Transport) |
| Registration Status | Currently Registered |
| Aircraft Registration Expiration Date | Dec 31, 2029 |
| Last FAA Update | Oct 6, 2026 |
| Registration Country | US |
| Registration State | UT |
| Weight Class | CLASS 3 |
| TC Data Sheet | — |
| TC Data Holder | — |
Accident & Incident History (NTSB)
No NTSB accident or incident record found for this aircraft.
See NTSB history for every Embraer ERJ 170-200 LR 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.
-
NONE
Apr 25, 2022
RIGHT HAND INBOARD SEAT TRACK AT SEAT 2C DOES NOT ALLOW PROPER ENGAGEMENT OF SEAT TRACK SPLICE DEVICE. (C-CHECK RO 5/4/2022) REMOVED RH INBOARD SEAT TRACK BEAM BETWEEN FRAMES 23-26. PERFORMED SPLICE REPAIR AS PER SRM. / RESTORED SURFACE PROTECTION. SEE CONTINUATION CARD FOR WORK PERFORMED. REF ETD2022-170-014281 REV A. SRM 53-00-10/REPAIR 01. WEIGHT OF REPAIR PARTS IS 201.6 GRAMS TOTAL. NO CHANGE TO WEIGHT AND BALANCE NOTED
-
NONE
Apr 7, 2022
CORROSION ON L/H BEAM SUPPORT BETWEEN FR 19 AND FR 20. (C-CHECK RO 5/4/2022) REMOVED AND REPLACED L/H BEAM SUPPORT BETWEEN FR 19 AND FR 20 REF SRM 51-40-08
-
NONE
Apr 7, 2022
LH INBOARD SEAT TRACK SECTION 23-34 HAS GOUGES AFT OF FRAMES 23, 24, 25, 30, 32 AND 33. (C-CHECK RO 5/4/2022) REMOVED GOUGES ONLH INBOARD SEAT TRACK SECTION 23-34. AFT OF FRAMES 23, 24, 25, 30, 32 AND 33. FOUND MAXIUM MATERIAL LOSS AT FRAMES 24, 25, AND 30 TO BE OUT OF ALLOW DAMAGE LIMITS.REF EMB SRM 53-21-10/AD01. PERFORMED CUT OUT OF CROWN TEETH FOR SEAT TRACK SPLICE DEVICE REPAIR AND INSTALLED REPAIRS AT FRAMES 24, 25, AND 30 REF EMB SRM 53-00-10/REPAIR02P SEE CONTINUATION CARD FOR DETAILS.
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON FRAME 90 CROSS BEAM LEFT END BELOW THE AFT END OF THE LH PANEL SUPPORT (X = -28€?). (C-CHECK RO 5/4/2022) REMOVED AND REPLACED FRAME 90 CROSS BEAM REF SRM 51-40-08
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA ON END OF LH INBOARD SEAT TRACK BETWEEN FRAME 84 AND 85. (C-CHECK RO 5/4/2022) BLENDED AND EVALUATED CORROSION, AFT WET AREA ON END OF LH INBOARD SEAT TRACK BETWEEN FR 84 AND 85. MEASUREMENTS 0.39"L X 0.33"W X 0.19"H. NOMINAL THICKNESS 0.363", REMAINING 0.173". ITEM IS OUT OF LIMITS PER REF 53-23-10AD04. REPAIRED IN ACCORDANCE TO ETD2022-170-013405.
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA ON END OF RH INBOARD SEAT TRACK BETWEEN FRAME 84 AND 85. (C-CHECK RO 5/4/2022) BLENDED AND EVALUATED CORROSION, AFT WET AREA ON END OF LH INBOARD SEAT TRACK BETWEEN FR 84 AND 85. MEASUREMENTS 0.39"L X 0.33"W X 0.75"H. NOMINAL THICKNESS 0.363", REMAINING 0.288". ITEM IS OUT OF LIMITS PER REF 53-23-10AD04. REPAIRED IN ACCORDANCE TO ETD2022-170-013405. SEE CONTINUATION CARD FOR WORK PERFORMED.
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON LH LONGITUDINAL FLOOR BEAM AT FRAME 87 WHERE THE BEAM PASSES BETWEEN THE LH AND CENTER SHEAR PANELS. (C-CHECK RO 5/4/2022) REMOVED AND REPLACED L/H LONGITUDINAL FLOOR BEAM AT FR 87. REF EMB SRM 51-40-08. SEE CONTINUATION FOR WORK PERFORMED.
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON RH LONGITUDINAL FLOOR BEAM AT FRAME 87 WHERE THE BEAM PASSES BETWEEN THE CENTER AND RH SHEAR PANELS. (C-CHECK RO 5/4/2022) REMOVED AND REPLACED R/H LONGITUDINAL FLOOR BEAM AT FR 87. REF EMB SRM 51-40-08. SEE CONTINUATION FOR WORK PERFORMED.
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON RH GUSSET PLATE AT FRAME 90 (X = +11€?). (C-CHECK RO 5/4/2022) REMOVED AND REPLACED AND RESTORED SURFACE PROTECTION AFT WET AREA RH GUSSET PLATE AT FRAME 90 REF SRM 51-40-08, 51-23-06
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON RH GUSSET PLATE AT FRAME 90 (X = +25€?). (C-CHECK RO 5/4/2022) REMOVED AND REPLACED AND RESTORED SURFACE PROTECTION AFT WET AREA RH GUSSET PLATE AT FR 90 REF SRM 51-40-08, 51-23-06
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON CENTER SPLICE PLATE AT FRAME 90 (X = -4€?). (C-CHECK RO 5/4/2022) REMOVED AND REPLACED CENTER SPLICE PLATE AT FR 90. REF EMB SRM 51-40-08. SEE CONTINUATION FOR WORK PERFORMED.
-
NONE
Apr 6, 2022
CORROSION, AFT WET AREA, ON RH SPLICE PLATE AT FRAME 89 (X = +11€?). (C-CHECK RO 5/4/2022) REMOVED AND REPLACED R/H SPLICE PLAT AT FR 89. REF EMB SRM 51-40-08. SEE CONTINUATION FOR WORK PERFORMED.
-
UNKNOWN
Aug 13, 2019
AFT FLIGHT ATTENDANT REPORTED SMOKE LIKE SMELL IN AFT CABIN. FLIGHT CREW REPORTS NO SMOKE DETECTOR MESSAGES OR WARNINGS. NO REPORTS OF SMOKE SEEN. NO ODD ENGINES PARAMETERS NOTED. LANDING NORMAL. (FLT5934) CONFIRMED WITH CREW THAT APU BLEED WAS OFF. PERFORMED ENGINE RUNS IAW AMM. OPERATED EACH ENGINE WITH ENGINE BLEEDS ON AT MULTIPLE POWER SETTINGS AS WELL AS OPERATED BOTH PACKS INDIVIDUALLY AT FULL HOT AND WAS UNABLE TO DUPLICATE DISCREPANCY.
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.
No FAA AIDS incident reports found for this aircraft.
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.
