Engine model · Turbo-fan · registry code 30016

Manufacturer (registry)
GE
Model
CFM56 SERIES
Registry code
30016
Type
Turbo-fan
Power
9,800 lb thrust

The registry names only the engine series, so ADs for every model in the series are matched.

On this page

Airworthiness directives that may apply · 0

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

No ADs matched this model

Registered aircraft · 28

See all 28 registered aircraft
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 engine_model_code IN ('30016')
  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 · 14

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

NTSB DCA10WA054Incident · No injuriesForeign investigationBoeing 737-300 · Riyadh, Saudi ArabiaOn April 24, 2010, a Mirage Aviation Boeing 737-300, registration N444HE, experienced a dual engine power loss shortly after rotation from runway 33R at King Khaled International Airport (OERK), Riyadh, Saudi Arabia. The airplane made an emergency return to…Apr 24, 2010 · N444HE · Minor damageNTSB WPR10LA134Accident · Serious injuriesLimited investigationFinal reportBoeing 737-7H4 · Santa Clarita, CAThe pilot’s abrupt airplane pitch change maneuver. Contributing to the accident was the flight crew’s failure to maintain the heading specified by the air traffic controller, which would have avoided the near collision course with an unidentified airplane…Feb 13, 2010 · N221WN · No damageNTSB DCA09FA047Accident · Minor injuriesField investigationFinal reportAirbus A320 · Denver, COThe first officer’s excessive pitch-up of the airplane while landing with a tailwind, which resulted in a tailstrike following a bounced landing. Contributing to the bounced landing were a high descent rate and excessive thrust resulting from the first…May 4, 2009 · N311US · Substantial damageNTSB DEN08IA022Incident · No injuriesIncident investigationFinal reportDouglas DC-8-73F · Wichita, KSFailure of the recirculation fan motor end ball bearing.Nov 2, 2007 · N880UP · Minor damageNTSB CHI07FA020Accident · No injuriesField investigationFinal reportBoeing 737-300 · Chicago, ILThe pilot-in-command of the other airplane failed to maintain clearance with the parked airplane during taxi for takeoff.Nov 7, 2006 · N328UA · 2 aircraft · Substantial damageNTSB CHI06LA161Accident · No injuriesLimited investigationFinal reportBoeing 737-300 · New York, NYThe foreign object damage to the horizontal stabilizer during taxi as a result of improper airport maintenance by contract maintenance personnel. The aluminum plate was a factor.Jun 8, 2006 · N403TZ · Substantial damageNTSB CHI04LA126Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · St. Louis, MOThe inadvertent encounter with turbulence which resulted in the injury to the flight attendant.Apr 10, 2004 · N662SW · No damageNTSB NYC03CA169Accident · Serious injuriesData collectionFinal reportBoeing 757-251 · Wadsworth, OHAn in-flight encounter with turbulence.Jul 22, 2003 · N504US · No damageNTSB 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 MIA98IA193Incident · No injuriesIncident investigationFinal reportBoeing 737-7H4 · Birmingham, ALThe improper electronic control unit software logic that permitted the electronic control unit to lock on a failed hydromechanical resolver, which failed due to damage to a wire that was incurred during the manufacturing process, resulting in an uncommanded…Jul 7, 1998 · N701GS · Minor damageNTSB CHI97LA162Accident · Serious injuriesLimited investigationFinal reportBoeing 737-300 · Valparaiso, INa delay by the pilot of the other aircraft in turning on his mode C transponder.Jun 8, 1997 · N321UA · No damageNTSB LAX97FA164Accident · Serious injuriesField investigationFinal reportBoeing 737-3S3 · Las Vegas, NVinadequate service provided by the TRACON controller, by issuing a radar vector to the Boeing 737 flight, which resulted in inadequate separation from a Beech 99 that the controller had just terminated from radar service; and failure of the controller to…Apr 19, 1997 · N313AW · No damageNTSB NYC93IA017Incident · No injuriesIncident investigationFinal reportBoeing 737-300 · Pittsburgh, PAThe high cycle fatigue failure of blades on the stage 1 high pressure compressor, which resulted in blade fracture and subsequent internal engine damage and fire.Oct 12, 1992 · N586US · No damageNTSB NYC92LA018Accident · Serious injuriesLimited investigationFinal reportBoeing 737-4B7 · Boston, MAA latch failure on a door in the aft galley which allowed a liquor kit to roll forward.Oct 23, 1991 · N441US · 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.engine_model_code IN ('30016')
  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 · 82

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

See all 82 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 engine_model_code IN ('30016')
  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 · 5,028

See all 5,028 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 engine_model_key = 'CFM56'
  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.