Skip to content

Public Record · As of May 5, 2026

N173MS

Bell 206-L4 · 2000 View Type →

Status

Registration Valid

Type

Rotorcraft

Engine

ALLISON 250-C30 SER

Last Cert Issue

—

Aircraft Resources

Manufacturer · Bell Textron → Engine · Rolls-Royce M250 (Allison) → Search FAA TCDS for BELL 206-L4 →

01 /  Registration

Filed with the Federal Aviation Administration

Every cell below is a literal field from the FAA Aircraft Registry. Click any value to open the FAA registry record for N173MS.

Tail Number

N173MS

Serial Number

52256

Make

BELL

Model

206-L4

Year of Manufacture

2000

Mfr / Model Code

1182110

Type Aircraft

Rotorcraft

Type Engine

Turbo-shaft

Engines

1

Seats

7

Engine Manufacturer

ALLISON

Engine Model

250-C30 SER

Horsepower

650 hp

Weight Class

CLASS 1

Certification

Standard (+1 flag) · code 1N

Registrant

FLORIDA KEYS MOSQUITO CONTROL DISTRICT · Government

Address

503 107TH STREET GULF · MARATHON, FL 33050-3021

FAA Region

7 · County 087

Status

Registration Valid

Airworthiness Date

—

Cert Issue Date

—

Expiration Date

—

Last FAA Action

—

Mode S Hex (ICAO24)

A12576

Mode S (Octal)

50222566

Live position via ICAO24 A12576

ADS-B Exchange → FlightAware → FlightRadar24 →

External services. Live tracks are unaffiliated with TallyAero or the FAA.

02 /  NTSB Records

Events on file with the National Transportation Safety Board

03 /  Airworthiness Directives

Applicable to BELL 206-L4

Federal Aviation Administration airworthiness directives matched to make and model. Each entry links to the Federal Register publication.

No matching airworthiness directives are on file for this make and model in the Federal Register.

04 /  Service Difficulty Reports

FAA SDR filings

The FAA does not currently expose a public API for Service Difficulty Reports. We do not back-fill or paraphrase. Search the FAA SDR portal directly →

05 /  Sources & Methodology

Every fact on this page links to its primary US-government source

We render only what the agency publishes. Found a factual error? Report it → We acknowledge within 5 business days and resolve within 14.