NTSB investigations: Lycoming 0-540 series, 1999

35 cases on aircraft whose registry engine model is Lycoming 0-540 series. Aircraft are matched to the registry by N-number and event date, checked against the reported serial number, make and model, so older matches can be wrong.

Cases per year

19642026
NTSB investigations: Lycoming 0-540 series, 1999 per year, 1964–2026: 3,541 cases
1964146
1965151
1966150
1967192
1968128
1969110
1970110
1971118
1972115
197383
197498
197583
197677
197797
197878
197992
198082
198180
198258
198359
198451
198559
198629
198747
198841
198935
199039
199131
199228
199326
199441
199541
199641
199726
199830
199935
200035
200140
200252
200339
200435
200539
200643
200730
200838
200937
201028
201137
201224
201315
201431
201524
201627
201725
201825
201932
202024
202128
202225
202330
202423
202525
202623

Latest cases

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_case_detail.parquet' c LEFT JOIN 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' a ON a.case_mkey = c.\"mKey\" AND a.position = 1
  WHERE year(c.\"eventDate\") = 1999
    AND c.\"mKey\" IN (SELECT x.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_aircrafts.parquet' x WHERE x.engine_model_code IN ('41532'))
  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.

NTSB MIA00FA058Accident · 2 fatalField investigationFinal reportAero Commander 500 · Georgetown, SCThe noninstrument-rated pilot's improper decision to attempt VFR flight into known instrument flight conditions, willful disregard of FAA Automated Flight Service Station weather forecast/weather observations, failure to maintain airspeed (VSO) while…Dec 22, 1999 · N6261B · DestroyedNTSB NYC00LA045Accident · Minor injuriesLimited investigationFinal reportCessna TR 182 · Clarksville, MDDeer that entered the runway environment while the pilot was executing a takeoff.Dec 5, 1999 · N5260S · Substantial damageNTSB MIA00LA034Accident · No injuriesLimited investigationFinal reportCessna 182RG · Jacksonville, FLThe pilot's failure to complete the before landing checklist and extend the landing gear, resulting in a gear up landing. A factor in the accident is the failure of the landing gear warning circuit to activate the cockpit warning horn.Nov 30, 1999 · N1818R · Substantial damageNTSB MIA00LA020Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Raleigh, NCThe pilot's failure to maintain directional control on landing rollout for undetermined reasons. This resulted in the airplane veering off the runway and colliding with an airport sign.Nov 3, 1999 · N8515W · Substantial damageNTSB FTW00LA018Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Oklahoma City, OKThe failure of the pilot to follow the landing checklist and verify that the landing gear was down and locked, which resulted in a wheels up landing. A factor was the failure of the landing gear locking mechanism for an undetermined reason.Oct 22, 1999 · N6774P · Substantial damageNTSB SEA00LA003Accident · No injuriesLimited investigationFinal reportMaule M-5-235C · Laurel, MTThe pilot's inadequate compensation for wind conditions. Factors include a dust devil/whirlwind at the location where the pilot was trying to land.Oct 21, 1999 · N6147M · Substantial damageNTSB SEA00LA006Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · Bozeman, MTThe pilot-in-command's (CFI) failure to take remedial action. Factors include the private pilot letting the airspeed get too low.Oct 20, 1999 · N8078P · Substantial damageNTSB MIA00LA011Accident · No injuriesLimited investigationFinal reportRobinson R-44 · Ft. Lauderdale, FLThe PIC's improper use of cyclic control during landing which resulted in a main rotor strike of the terrain and the rotorcraft's tail boom.Oct 19, 1999 · N8364Z · Substantial damageNTSB LAX00LA019Accident · No injuriesLimited investigationFinal reportCessna TR182 · Fresno, CAInadequate maintenance inspection mandated by the FAA, and the inadequate design of the exhaust heater core/muffler and deflectors that failed to divert hot exhaust gasses away from the battery and cabin heat valve.Oct 19, 1999 · N756LE · Substantial damageNTSB MIA99LA274Accident · No injuriesLimited investigationFinal reportPiper PA-28-236 · St. Augustine, FLThe inadvertent inflight collision with a bird resulting in substantial damage to the right wing outboard leading edge.Sep 25, 1999 · N9123P · Substantial damageNTSB MIA99LA255Accident · Minor injuriesLimited investigationFinal reportPiper PA-24-250 · St. Petersburg, FLthe pilots improper use of the hand brake during the landing roll out and his failure to maintain directional control, which resulted in the airplane exiting the runway and incurring substantial damage.Sep 12, 1999 · N8051P · Substantial damageNTSB LAX99LA290Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Boulder City, NVthe student pilot's failure to maintain directional control of the airplane during the takeoff roll.Sep 1, 1999 · N8675W · Substantial damageNTSB DEN99LA146Accident · Minor injuriesLimited investigationFinal reportPiper PA-32-260 · Aspen, COThe pilot's inadequate in flight planning. Factors were the high density altitude, the lack of suitable terrain for a forced landing, and the sign post that the right wing impacted.Aug 16, 1999 · N991RC · DestroyedNTSB NYC99LA189Accident · No injuriesLimited investigationFinal reportPiper PA24-250 · Greencastle, PAThe pilot's misjudgement of speed and distance during the approach and his failure to perform a go around.Jul 31, 1999 · N5801P · Substantial damageNTSB FTW99LA197Accident · Serious injuriesLimited investigationFinal reportPiper PA-25-235 · Fabens, TXThe pilot's inadvertent flight into adverse weather conditions. A factor was the windshear weather conditions.Jul 22, 1999 · N6736Z · Substantial damageNTSB IAD99LA053Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Zanesville, OHThe pilot not maintaining a proper descent rate and an inadequate flare.Jul 18, 1999 · N235TL · Substantial damageNTSB NYC99LA179Accident · No injuriesLimited investigationFinal reportAllen-Charles Barracuda · Hermon, NYThe pilot's inadequate preflight planning which resulted in a precautionary landing. A factor in this accident was the pilot's selection of unsuitable terrain for the precautionary landing.Jul 17, 1999 · N849JA · Substantial damageNTSB DEN99LA118Accident · No injuriesLimited investigationFinal reportPiper PA-25-235 · Delta, UTThe pilot's delayed aborted takeoff. A factor was the high density altitude.Jul 12, 1999 · N7614Z · Substantial damageNTSB CHI99LA230Accident · No injuriesLimited investigationFinal reportPiper PA-25-235 · Fargo, NDthe altitude/clearance not maintained by the pilot.Jul 12, 1999 · N4652Y · Substantial damageNTSB CHI99LA229Accident · No injuriesLimited investigationFinal reportPiper PA-25-235 · Lefor, NDthe altitude/clearance not maintained by the pilot.Jul 12, 1999 · N7329Z · Substantial damageNTSB SEA99LA083Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Plentywood, MTThe pilot's failure to ensure that the landing gear were properly down and locked for landing.Jun 9, 1999 · N5309P · Substantial damageNTSB CHI99LA173Accident · No injuriesLimited investigationFinal reportAero Commander 500 · Effingham, ILinadvertent wheels-up landing and the checklist not followed by the pilot. The landing gear lever not engaged was an additional cause.Jun 4, 1999 · N711NE · Substantial damageNTSB CHI99LA154Accident · No injuriesLimited investigationFinal reportCessna R182 · Chesterfield, MOthe pilot's failure to attain clearance over the fence. Factors associated with the accident were the pilot's inadequate compensation for the wind conditions which resulted in a loss of directional control, the crosswind, and the fence posts.May 16, 1999 · N738WK · Substantial damageNTSB ATL99LA082Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Southern Pines, NCA failure of the left main landing gear retraction assembly as a result of the disconnection of the left main landing gear strap bracket assembly from the main gear spring attachment bracket due to the missing nut. A factor was the ditch.May 8, 1999 · N7001P · Substantial damageNTSB FTW99LA136Accident · No injuriesLimited investigationFinal reportPiper PA-28-235 · Sulphur Springs, TXThe delayed aborted takeoff by the pilot-in-command. Factors were the short runway, the tall grass, and the tree.May 7, 1999 · N9009W · Substantial damageNTSB DEN99LA065Accident · Minor injuriesLimited investigationFinal reportPiper PA-25-235 · Wendover, UTThe pilot's improper preflight/in-flight planning and decision making, resulting in fuel supply exhaustion. A factor was the closed runway condition.Apr 26, 1999 · N906DS · Substantial damageNTSB LAX99LA159Accident · No injuriesLimited investigationFinal reportCessna R182 · San Luis Obispo, CAThe inadequate preflight inspection of the aircraft by the pilot-in-command which resulted in a loss of engine power due to water contamination in the fuel system. A factor in the accident was an improper maintenance alteration which disabled a fuel sump…Apr 21, 1999 · N7317X · Substantial damageNTSB ANC99LA041Accident · No injuriesLimited investigationFinal reportMaule M-5 · Talkeetna, AKThe pilot's inadequate compensation for the crosswind during landing. Factors associated with this accident were the left crosswind, and the snowbank on the edge of the runway.Apr 4, 1999 · N9237E · Substantial damageNTSB MIA99LA116Accident · Serious injuriesLimited investigationFinal reportMaule M-7-235B · Boca Grande, FLThe pilots failure to maintain a visual lookout on landing resulting in an in-flight collision with a wave.Apr 3, 1999 · N10430 · Substantial damageNTSB MIA99LA099Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Atlantic Ocean (Atlantic Ocean)a loss of engine power for an undetermined reason, resulting in a forced landing in water, and subsequent sinking of the airplane.Mar 3, 1999 · N4802S · DestroyedNTSB MIA99LA089Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Everglades City, FLThe failure of the PIC to maintain directional control on takeoff roll following a loss of power brought about by fuel starvation due to the PIC's failure to verify the proper setting of the fuel selector valve, and the subsequent collision with trees during…Feb 21, 1999 · N8309P · Substantial damageNTSB FTW99LA073Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Denton, TXThe hard landing as a result of the pilot's failure to maintain the proper descent rate during the landing flare.Feb 7, 1999 · N112WS · Substantial damageNTSB MIA99LA073Accident · Serious injuriesLimited investigationFinal reportPiper PA-32-260 · Orlando, FLA loss of engine power due to an engine assembly overload for undetermined reasons. A related factor was the pilot exceeded the airplane's maximum allowable weight.Feb 3, 1999 · N5528J · DestroyedNTSB CHI99LA065Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · St. Charles, ILA loss of engine power due to fuel exhaustion. Also causal was the pilot's inadequate preflight/planning preparation which led to inadvertent flight into instrument meteorological conditions and him becoming lost/disoriented. Contributing to the accident were…Jan 17, 1999 · N40712 · Substantial damageNTSB ATL99LA037Accident · No injuriesLimited investigationFinal reportPiper PA-24-250 · Colbert, GAInadequate planning/decision by the pilot, which resulted in fuel exhaustion due to an inadequate supply of fuel.Jan 2, 1999 · N7295P · Substantial damage