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.
Airbus Helicopters EC135 / H135
N200HN · Serial 0444
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
- N200HN — Sep 9, 2026 to present
Full FAA Registration Record
| Serial Number (as registered) | 0444 |
|---|---|
| Aircraft Unique ID Number | 00220889 |
| FAA Manufacturer / Model Code | 5620032 |
| Aircraft Engine Type | Turboshaft |
| Certification of Aircraft Registration Date | Mar 18, 2013 |
| Registration Status | Currently Registered |
| Aircraft Registration Expiration Date | Mar 31, 2029 |
| Last FAA Update | Oct 16, 2026 |
| Registration Country | US |
| Registration State | CO |
| Weight Class | CLASS 2 |
| TC Data Sheet | H88EU |
| TC Data Holder | AIRBUS HELICOPTERS DEUTSCHLAND GMBH (AHD) |
Accident & Incident History (NTSB)
No NTSB accident or incident record found for this aircraft.
See NTSB history for every Airbus Helicopters EC135 / H135 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
Aug 31, 2022 (possible match)
AFTER LANDING, CREW SMELLED AN ELECTRICAL BURNING ODOR IN THE CABIN, WHICH WAS ELIMINATED IMMEDIATELY UPON OPENING THE CABIN DOORS. NORMAL SHUTDOWN WAS COMPLETED. WHEN BASE MECHANIC ARRIVED, WE SEARCHED FOR A SOURCE OF THE SMELL AND WHEN NONE WAS FOUND, WE RAN-UP THE AIRCRAFT WITH ALL ELECTRICAL COMPONENTS ON AND COULD NOT REPRODUCE THE ODOR. AIRCRAFT WAS RETURNED TO SERVICE. I SUSPECT THAT THE ODOR DID NOT ORIGINATE FROM THE AIRCRAFT, BUT RATHER FROM THE HOSPITAL'S PLANT OPS, WHICH WAS DIRECTLY UPWIND OF THE 5TH FLOOR HELIPAD. POSSIBLY FROM WELDING.
-
SKIN
Nov 10, 2021 (possible match)
SIGNIFICANT CORROSION WAS DISCOVERED ON THE FUSELAGE LH SKIN (P/N: L533M1007237) ADJACENT TO THE AFT LOWER MAINTENANCE STEP (APPROX. STA 47095290 AND WL 1600-1800)
-
FRAME
Oct 25, 2021 (possible match)
DAMAGE TO FRAME 1 (PN: L533M1011212) IN THE FORM OF EXTENSIVE CORROSION ACROSS THE LOWER FLANGE
-
KEELBEAM
Oct 11, 2021 (possible match)
FUSELAGE - LOWER SECTION - RH KEEL BEAM CAP CORROSION - DAMAGE TO THE RH KEEL BEAM CAP (PN: L533M1010203) IN THE FORM OF CORROSION ON THE LOWER SURFACE OF THE HORIZONTAL FLANGE. THE DAMAGE IS LOCATED AS APPROXIMATELY X2200, AND WAS MEASURED TO BE APPROXIMATELY 0.75” X 0.25” AND 0.024” DEEP AT THE DEEPEST POINT
-
FRAME
Oct 11, 2021 (possible match)
FRAME 5 CRACK FOUND ON L/H FWD LOWER SIDE OF METRO BOX BEAM ASSY. CRACK LENGTH IS .75 INCHES
-
FLOOR SKIN
Oct 11, 2021 (possible match)
FUSELAGE - COCKPIT FLOOR - OUTER SKIN DELAMINATION AND CORROSION DAMAGE - DAMAGE TO THE COCKPIT FLOOR (PN: L533M1013107) IN THE FORM OF AN AREA OF DELAMINATION ON THE UPPER SKIN PANEL MEASURED TO BE APPROXIMATELY 3.0” X 1.25”, AS WELL AS AN AREA OF CORROSION ON THE UPPER SKIN PANEL AT THE FWD GROUNDING POINT MEASURING APPROXIMATELY 1.0” X 1.0”.
-
GEARBOX
Feb 6, 2020 (possible match)
MGB CHIP INDICATION AT START UP. PERFORMED INSPECION OF MAG PICK UP AND OIL FILTER AND FOUND SIGNIFICNT METAL. SENT CHIPS AND OIL FOR ANALYSIS. ZF TECHNICAL STAFF FOUND METAL TO BE FROM LOWER MAST BEARING SPINNING IN BORE. THEY RECOMENED MGB BE SENT IN FOR REPAIR. THEY NOTED THIS IS SOMETHING THEY’VE ONLY SEE 1-2 TIMES IN 20 YEARS.
-
SEAT TRACK
Jul 10, 2019 (possible match)
AFT CABIN FLOOR, CORROSION ON LT INBOARD SEAT TRACK IN MULTIPLE AREAS.
-
TRANSMISSION
Dec 20, 2017 (possible match)
TWO MAIN TRANSMISSION CHIP INDICATIONS 35 HOURS APART REQUIRING PINION AND BEVEL GEAR INSPECION PER AIRBUS ASB EC135-63A-012. FOUND PITTING ON #1 BEVEL GEAR THAT WAS BEYOND LIMITS. THIS AIRCRAFT REMAINS OUT OF SERVICE AT THE TIME OF THIS SUBMISSION AWAITING A REPLACEMENT MAIN TRANSMISSION TO ARRIVE.
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.
