Boeing 737-3TO

Aircraft model · Fixed wing multi engine · Airplane · registry code 138447G

Manufacturer (registry)
BOEING
Model
737-3TO
Registry code
138447G
Registered
2 aircraft
Type
Fixed wing multi engine
Engines
2 · Turbo-fan
Seats
149
Weight class
20,000 lb and over
Certification
Type certificated

Model codes come from the FAA registry’s reference file. ADs are matched to them by model name and maker.

On this page

Aircraft by year built · 60

1985Registered nowDeregistered2026
Aircraft by the year they were built: 60 aircraft
198516
198617
198722
19885

Airworthiness directives that may apply · 0

ADs whose products match this airframe model. Each AD’s applicability may narrow it by serial number, part number or configuration.

No ADs matched this model

Registered aircraft · 2

Query with SQL
duckdb -csv -c "SELECT n_number, serial_number, year_manufactured, status, registrant_name, registrant_city, registrant_state
  FROM 'https://openairdocs.org/data/latest/faa_aircraft_registration.parquet'
  WHERE aircraft_model_code IN ('138447G')
  ORDER BY n_number"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

NTSB investigations · 9

Aircraft matched to this model through the registry, by N-number and event date, checked against the reported serial number, make and model.

NTSB MIA99FA252Accident · No injuriesField investigationFinal reportBoeing B737-300 · West Palm Beach, FLThe fatigue fracture and separation of the high pressure turbine forward rotating air seal due to a manufacturing defect in a bolt hole that was not detected by the engine manufacturer due to inadequate and ineffective inspection techniques. Contributing to…Sep 12, 1999 · N17356 · Substantial damageNTSB NYC99LA076Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Newark, NJThe flight attendant's failure to follow cabin door opening procedures.Mar 17, 1999 · N17321 · No damageNTSB NYC99IA024Incident · No injuriesIncident investigationFinal reportBoeing 737-3TO · Newark, NJA loss of torque on the apex nut of the shimmy damper for undetermined reason(s), which resulted in a failure of the shimmy damper, and the subsequent failure of the lower torsion link of the right main landing gear.Nov 6, 1998 · N12318 · Minor damageNTSB MIA95LA133Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Tallahassee, FLThe failure of a passenger to comply with flight crew instructions to remain seated with her seat belt fastened which resulted in her being injured while walking in the aisle during a turbulence encounter.May 19, 1995 · N60312 · No damageNTSB FTW95IA053Incident · No injuriesIncident investigationFinal reportBoeing B-737-300 · Houston, TXThe failure of maintenance personnel to follow the taxi checklist resulting in the hydraulic pumps not being turned on.Nov 26, 1994 · N14336 · Minor damageNTSB MKC90IA070Incident · Minor injuriesIncident investigationFinal reportBoeing 737-300 · Wichita, KSImproper installation of level arm.Mar 17, 1990 · N17317 · Minor damageNTSB DCA89MA034Accident · No injuriesMajor investigationFinal reportBoeing 737-300 · Oakland, CAIgnition of puddled fuel from a blocked combustor drain line, and a slow start during which fuel was misted and blown out the tail pipe. An existing tailwind at the gate allowed the fuel to wet the tail surfaces and be ignited during the APU start. The…Mar 17, 1989 · N12318 · Substantial damageNTSB FTW88IA141Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Kenton, DEA flameout of the #1 engine occurred due to water ingestion when the aircraft penetrated a vip level 5 thunderstorm and encountered heavy rain while descending with the throttles a flight idle. The engine suffered overtemperature damage to the turbine section…Jul 26, 1988 · N14336 · Minor damageNTSB NYC88IA109Incident · No injuriesIncident investigationFinal reportBoeing 737 · Morristown, NJBoeing 737 (N69348) was depg newark intl arpt as a lear jet 24 (N500NH) was depg fm teterboro. Both were being ctld by new york TRACON (newark sector). The strip for the 737 was mismarked as a north departure rather than an east departure. The instructor/full…Mar 19, 1988 · N69348 · 2 aircraft · No damage
Query with SQL
duckdb -csv -c "SELECT c.\"ntsbNumber\", c.\"eventDate\", c.\"eventType\", c.\"eventCity\", c.\"eventStateOrRegion\", a.n_number, a.\"aircraftMake\", a.\"aircraftModel\", c.\"highestInjuryLevel\", c.\"totalFatal\", c.\"completionStatus\", c.report_url
  FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a JOIN 'https://openairdocs.org/data/latest/ntsb_case_detail.parquet' c ON c.\"mKey\" = a.case_mkey
  WHERE a.aircraft_model_code IN ('138447G')
  ORDER BY c.\"eventDate\" DESC, c.\"ntsbNumber\" DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

FAA incident reports · 75

Matched to this model through the registry, by N-number and event date, checked against the reported make and model.

See all 75 incident reports
Query with SQL
duckdb -csv -c "SELECT report_number, event_date, event_type, city, state, aircraft_make, aircraft_model, aircraft_damage, fatal_injuries, n_number
  FROM 'https://openairdocs.org/data/latest/faa_incident_report.parquet'
  WHERE aircraft_model_code IN ('138447G')
  ORDER BY event_date DESC, report_number DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.

Service difficulty reports · 223

See all 223 difficulty reports
Query with SQL
duckdb -csv -c "SELECT sdr_id, difficulty_date, n_number, aircraft_make, aircraft_model, part_name, part_condition, jasc_code, discrepancy
  FROM 'https://openairdocs.org/data/latest/faa_service_difficulty_report.parquet'
  WHERE aircraft_model_key = '7373TO'
  ORDER BY difficulty_date DESC"

Prints the whole list as CSV. It reads the release’s Parquet files over HTTPS, so there’s nothing to download first. Install DuckDB to run it.