- Manufacturer (registry)
- BOEING
- Model
- 737-3B7
- Registry code
- 138447F
- Registered
- 1 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 · 48
| 1984 | 5 |
|---|---|
| 1985 | 7 |
| 1986 | 5 |
| 1987 | 15 |
| 1988 | 8 |
| 1989 | 7 |
| 1992 | 1 |
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 · 1
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 ('138447F')
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.
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 ('138447F')
ORDER BY n_numberRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
NTSB investigations · 14
Aircraft matched to this model through the registry, by N-number and event date, checked against the reported serial number, make and model.
Of 2 cases NTSB coded with a defining event. All defining events
Findings NTSB made part of the probable cause. A case can have several. All findings
Of 12 cases with NTSB’s older coding, defined in its coding manual.
NTSB ENG09IA009Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Charlotte (CLT), NCThe failure of the left hand main landing gear was caused by heat induced cracks resulting from abusive grinding/polishing of the chrome plate that was applied during the last overhaul.NTSB ENG08IA051Incident · No injuriesIncident investigationFinal reportBoeing 737 · Phoenix (PHX), AZThe failure of the MLG was due to cracking in the cylinder wall resulting from a fatigue mechanism which initiated at, and near the inner diameter (ID) surface, with propagation through the wall toward the outer diameter(OD) surface. Crack initiation was due…NTSB NYC06FA184Accident · Minor injuriesField investigationFinal reportBoeing 737-300 · Pittsburgh, PAThe airplane tug driver's inadvertent movement of the tug gear shift lever from forward to reverse, which resulted in the nose landing gear collapse. Contributing to the accident was the defective gear shift lever.NTSB NYC05IA095Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Boston, MAThe local east controller's failure to follow FAA Order 7110.65, para 3-9-8 and Boston Tower Order 7110.11, Standard Operating Procedures, which resulted in a runway incursion during takeoff involving two transport category airplanes.NTSB NYC00LA097Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Boston, MAIn flight encounter with turbulence.NTSB NYC98IA165Incident · Minor injuriesIncident investigationFinal reportBoeing 737-300 · Mcconnellsburg, PAA high altitude encounter with wake vortices.NTSB MIA96LA220Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Chattanooga, TNclear air turbulence, which was encountered during cruise flight and resulted in injuries to passengers.NTSB NYC96IA022Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Portland, MEa bird strike during takeoff, which resulted in failure of several fan blades in the right engine and a partial loss of engine power.NTSB MIA95IA214Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Fort Lauderdale, FLLow electrical resistance of the autopilot aileron actuator for unspecified reasons which resulted in an uncommanded roll to the right.NTSB MIA95IA194Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Charlotte, NCImproper installation of the 'a' system flight control computer by company maintenance personnel, which resulted in pin connector(s) being pushed loose and subsequent malfunction of the autopilot.NTSB MIA95IA187Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Orlando, FLContamination of the wiring harness and electrical connectors to the E-1-2 and E-1-3 shelf disconnect brackets in the electronics compartment, which resulted in an electrical fault and an uncommanded roll malfunction of the autopilot. A factor relating to the…NTSB CHI93IA372Incident · No injuriesIncident investigationFinal reportBoeing 737-3B7 · Indianapolis, INan undetermined problem which resulted in the physical impairment of flight attendants, passengers and the first officer.NTSB NYC93LA040Accident · 1 fatalLimited investigationFinal reportBoeing 737-300LR · Flushing, NYA lack of adequate clearance between the walker and tug which resulted in the walker being struck by the tug when he fell for unknown reason(s). A factor related to the accident was the lack of a policy to stay clear of the tug, towbar, and nosewheel of the…NTSB DCA91MA018Accident · 34 fatalClass 1 · MajorFinal reportBoeing 737-300 · Los Angeles, CAThe failure of the Los Angeles air traffic facility management to implement procedures that provided redundancy comparable to the requirements contained in the national operational position standards and the failure of the FAA air traffic service to provide…
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 ('138447F')
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.
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 ('138447F')
ORDER BY c."eventDate" DESC, c."ntsbNumber" DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
FAA incident reports · 36
Matched to this model through the registry, by N-number and event date, checked against the reported make and model.
Accident 20060727030729ABoeing 7373B7 · Pittsburgh, PA(-23) During push back, nose gear collapsed. Aft nose wheel doghouse area broken. Pressure vessel bulkhead. Damage makes it an accident.Incident 20050702019319IBoeing 7373B7 · Richmond, VA(-23) An emergency descent was initiated after the cabin altitude warning was triggered as the aircraft climbed through 27,700FT, and the cabin altitude was confirmed climbing past 10,000FT. The aircraft landed without incident at ric, and taxied to the gate,…Incident 20040614021519IBoeing 7373B7 · Pittsburgh, PA(-23) On June 14, 2004, us airways' aircraft N393US, a Boeing 737-3B7, operated as flight 1076 from charlotte, north carolina to Pittsburgh, Pennsylvania (pit). At approximately 3:15 am local time, the aircraft landed in pit on runway 10L. At touchdown, the…
See all 36 incident reportsQuery 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 ('138447F')
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.
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 ('138447F')
ORDER BY event_date DESC, report_number DESCRun it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.
Service difficulty reports · 4,722
SDR I5EA2024020800003Battery Pack · no testAFT GALLEY EMERGENCY EXIT LIGHT INDICATORS INOP. REMOVED AND REPLACED EMERGENCY LIGHT BATTERY WITH SERVICEABLE UNIT AT STA 920 IAW B737-300 AMM 33-51-51. TEST OK.SDR I5EA2024020800002Battery Pack · no testEMERGENCY EXIT SIGN LIGHT AT STA 627R INOP. REMOVED AND REPLACED EMERGENCY EXIT SIGN LIGHT BATTERY WITH SERVICEABLE UNIT M1135 AT STA. 622R IAW B737-300 AMM 33-51-51. TEST OK.SDR I5EA2024020700001Battery Pack · no testEMERGENCY LIGHT INOP AT R-1 DOOR. REMOVE AND REPLACED EMERGENCY LIGHT BATTERY PACK M1133 AT STA.330L IAW B737-300 AMM 33-51-51. TEST GOOD.
See all 4,722 difficulty reportsQuery 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 = '7373B7' 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.
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 = '7373B7' ORDER BY difficulty_date DESC
Run it at the DuckDB prompt, or in any tool that reads Parquet over HTTPS. More ways to query the release are on Use the data.