NTSB investigations, MD
43 cases where the first occurrence was “In flight collision with object”.
Cases per year
| 1982 | 1 |
|---|---|
| 1983 | 4 |
| 1984 | 2 |
| 1985 | 4 |
| 1986 | 1 |
| 1987 | 7 |
| 1988 | 2 |
| 1989 | 5 |
| 1991 | 2 |
| 1992 | 1 |
| 1993 | 2 |
| 1994 | 2 |
| 1996 | 1 |
| 1997 | 3 |
| 1998 | 1 |
| 1999 | 1 |
| 2002 | 1 |
| 2005 | 1 |
| 2006 | 2 |
Where
Open the mapLatest 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 c.\"eventStateOrRegion\" = 'MD' AND c.\"eventCountry\" = 'USA'
AND c.\"mKey\" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o.\"occurrenceNumber\" = 1 AND o.\"occurrenceCode\" = 220)
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_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 c."eventStateOrRegion" = 'MD' AND c."eventCountry" = 'USA' AND c."mKey" IN (SELECT o.case_mkey FROM 'https://openairdocs.org/data/latest/ntsb_occurrences.parquet' o WHERE o."occurrenceNumber" = 1 AND o."occurrenceCode" = 220) ORDER BY c."eventDate" DESC, c."ntsbNumber" 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.
NTSB NYC07FA042Accident · 2 fatalField investigationFinal reportCessna 210K · Edgewater, MDThe pilot's failure to maintain the proper altitude/clearance will on approach, which resulted in an in-flight collision with trees. Contributing to the accident was the night-light conditions, an obstruction light that was not illuminated, and trees that had…NTSB NYC06LA160Accident · 1 fatalLimited investigationFinal reportAerial Productions Intl. Acrojet Special · Ocean City, MDThe pilot's failure to maintain adequate airspeed which resulted in a stall mush and subsequent impact with trees. A factor in the accident was windshear, and the high weight of the airplane.NTSB NYC05CA076Accident · No injuriesData collectionFinal reportPiper PA-28-140 · Indian Head, MDThe pilot's failure to maintain adequate altitude/clearance while on final approach, which resulted in an in-flight collision with trees. A factor in this accident was the gusty wind conditions.NTSB IAD02FA052Accident · 1 fatalField investigationFinal reportAyres S-2R · Swanton, MDThe pilot's failure to maintain visual separation from a set of known, yet unmarked power lines.NTSB IAD99FA069Accident · Serious injuriesField investigationFinal reportCessna 150M · Ellicott City, MDthe flight instructor's failure to follow the balked landing procedure in the owner's manual by retracting the flaps from 40 degrees to zero degrees.NTSB IAD99FA020Accident · 1 fatalField investigationFinal reportBurgess RV-6 · Edgewater, MDThe pilot's failure to maintain adequate altitude/clearance from the trees. Contributing to the accident was the pilot's unfamiliarity with the geographic location and dark night conditions.NTSB NYC98LA029Accident · Serious injuriesLimited investigationFinal reportBeech E33A · Westminster, MDthe pilot's improper in-flight planning/decision, his misjudgment of speed and distance while on final approach to land, and his delay in aborting the landing after failing to attain a proper touchdown point for landing.NTSB IAD97LA062Accident · Minor injuriesLimited investigationFinal reportSchweizer SGS-233A · Woodbine, MDThe pilot misjudged his altitude during approach.NTSB NYC97LA053Accident · Minor injuriesLimited investigationFinal reportPiper PA-38-112 · Nanjemoy, MDthe pilot's inadequate compensate for the wind conditions and failure to maintain adequate obstacle clearance during the initial climb after takeoff. The unfavorable wind condition and proximity of trees were related factors.NTSB NYC97LA031Accident · No injuriesLimited investigationFinal reportCessna 152 · Baltimore, MDthe student pilot's premature rotation and inadequate supervision by the flight instructor (CFI), which resulted in failure of the flight crew to obtain adequate airspeed during takeoff for a proper rate of climb. Trees at the departure end of the runway were…NTSB BFO94FA160Accident · 1 fatalField investigationFinal reportBeech A36 · Barstow, MDThe pilot's failure to maintain clearance from the tower.NTSB NYC94LA109Accident · Serious injuriesLimited investigationFinal reportCessna 172N · Princess Anne, MDThe pilot's failure to do a go-around and her delay in the initiating of an aborted landing, which resulted in her failure to outclimb trees during the aborted landing.NTSB BFO93FA129Accident · 1 fatalField investigationFinal reportPiper PA-28-180 · California, MDThe pilot initiating VFR flight in instrument meteorological conditions. Factors which contributed to the accident were: the pilot's failure to obtain a weather briefing, his lack of sleep, and the existing weather conditions.NTSB NYC93LA132Accident · No injuriesLimited investigationFinal reportPiper PA-30 · Mitchellville, MDThe failure of the pilot to maintain a proper glide path during the final approach, which resulted in the airplane striking a moving vehicle.NTSB BFO92FA031Accident · 2 fatalField investigationFinal reportCessna 210K · Frederick, MDThe pilot's improper IFR operation and descent below the ILS glideslope and decision height, which resulted in an inflight collision with trees. The weather condition and lack of a recent weather briefing were related factors.NTSB BFO91LA064Accident · No injuriesLimited investigationFinal reportChampion 7KCAB · Berlin, MDThe unsuitable placement of two banners (improper planning) by other personnel causing an unintentional pickup of both banners.NTSB BFO91LA036Accident · No injuriesLimited investigationFinal reportHughes 369HS · Columbia, MDThe pilot's inadequate visual lookout, which resulted in his failure to see-and-avoid the obstruction (fence post).NTSB BFO90LA005Accident · Minor injuriesLimited investigationFinal reportBellanca 8GCBC · Churchville, MDThe pilot not maintaining adequate clearance from the wind sock during an aborted landing. A contributing factor was the presence of another aircraft.NTSB BFO89DIG02Accident · Minor injuriesFinal reportPiper PA-28 · Cumberland, MDThe pilot's improper decision to takeoff in deteriorating weather conditions. Related factors were: the pilot's failure to obtain a weather briefing prior to departure, and his lack of an instrument rating.NTSB BFO89LA049Accident · No injuriesLimited investigationFinal reportBell 47J · Fruitland, MDPoor judgement of the pilot by flying, while physically impaired by alcohol, and his misjudgement of clearance between the helicopter and the structure. The dark night and object (structure) were considered to be contributing factors.NTSB BFO89FA033Accident · 2 fatalField investigationFinal reportBell UH-1B · Oldtown, MDFailure of the pilot to see-and-avoid the obstruction (inadequate visual lookout). Factors related to the accident were: the obstruction (static wires), and the lack of visual cues for the pilot to detect the wires.NTSB BFO89LA026Accident · Minor injuriesLimited investigationFinal reportCessna 172H · Odenton, MDThe inflight collision with birds.NTSB BFO88DIG03Accident · Serious injuriesFinal reportGrumman G-164A · Sleepy Creek, MDDuring the aerial application flight the airplane struck and severed three power lines. The pilot stated he did not see the lines until it was too late. The airplane caught fire and continued on its flight path crossing a highway and a river. The airplane…NTSB BFO88FA025Accident · No injuriesField investigationFinal reportCessna 150E · Mitchellville, MDThe student plt elected to initiate the flt even though the flaps malfunctioned during the previous flt. Shortly after takeoff the plt was unable to keep the flaps in the extended position. The plt had not been feeling well on the morning of the flt and felt…NTSB BFO88LA018Accident · No injuriesLimited investigationFinal reportPiper PA-32-300 · Churchton, MDThe plt rprtd that after searching unsuccessfully for a wind sock & getting no reply on UNICOM freq, he made an apch to rwy 16. Later, he saw the wind sock about half way down the rwy near a building. Drg the apch, he noticed he was high & put the acft in a…NTSB BFO87FA050Accident · Minor injuriesField investigationFinal reportCessna 172P · Whitemarsh, MDThe pilot stated that he touched down near the end of the 22OO foot runway. However, witnesses said he landed so FAR down the runway that they did not believe he could stop on the runway. The pilot delayed his go around attempt to the point where it was not…NTSB BFO87DIG08Accident · Minor injuriesFinal reportPiper PA-28 · Mitchellville, MDDuring takeoff, the acft hit the tops of trees near the departure end of the rwy. The plt stated that after clipping the treetops, he knew the acft was 'going in,' so he pulled the yoke back to slow it as much as possible. Also, the plt stated that during…NTSB BFO87LA041Accident · 1 fatalLimited investigationFinal reportPiccard AX-6 · Gaithersburg, MDAfter two aborted landings the pilot saw a field in the distance and attempted to land. Although two other balloons had landed nearby, the field he was blown towards had numerous powerlines surrounding it, some of them at treetop height. During the approach…NTSB BFO87FIG04Accident · No injuriesFinal reportAyres S2R-T15 · Grantsville, MDThe acft was second in a flt of three spraying forest area with dimilin when it contacted a power line suspended between two hilltops. The prop severed the single strand of cable and shortly after the engine lost power. The plt maneuvered for an emgcy lndg,…NTSB BFO87LA036Accident · No injuriesLimited investigationFinal reportBeech C-24R · Chestertown, MDThe pilot, unfamiliar with the airport, intended to perform a trial takeoff run to determine how the aircraft accelerated on the grass runway. During the trial run when the aircraft was about half way down the runway, the pilot felt the aircraft was ready to…NTSB BFO87LA034Accident · Minor injuriesLimited investigationFinal reportAyres Turbo Thrush 52R34 · Lavale, MDWhile spraying for gypsy moths during the early morning, the turbo-thrush collided with static wires located on top of high tension lines. The pilot stated that he did not see the wires because they were located on the shady side of an adjacent mountain.NTSB BFO87FA006Accident · Minor injuriesField investigationFinal reportPiper PA-28-140 · Bloomington, MDWitnesses observed 2 aircraft flying near treetop level and reported that one appeared to be about 10 feet behind the other. The lead aircraft collided with trees when the pilot delayed his pullup to a point where he was unable to climb over a ridge on his…NTSB BFO86FA006Accident · 1 fatalField investigationFinal reportEipper Quicksilver MXL II · Parkton, MDWitnesses in the area observed the vehicle flying in the local area at other times however this was the first time they had seen two people in it. They also observed the vehicle flying erratically after liftoff and noted that the winds were gusty. Upon…NTSB BFO86FA002Accident · 1 fatalField investigationFinal reportPiper PA-32RT-300T · Gaithersburg, MDThe plt was clrd for a VOR rwy 14 apch. On apch, he rprtd at the sleet intxn (a fix on the NDB apch). The acft was then seen flying ovr the arpt on an easterly hdg. UNICOM operator said he then heard the plt call "turning final." However, bfr lndg, the acft…NTSB BFO85LA066Accident · No injuriesLimited investigationFinal reportCessna 152 · Gaithersburg, MDAfter not obtaining surface wind info and not observing the wind sock, the student plt entered final apch without observing any significant drift. When the acft was at nose-up attitude. It floated and stopped descending for a few seconds. Suddenly, the plt…NTSB BFO85LA033Accident · No injuriesLimited investigationFinal reportMooney M20E · Mitchellville, MDAfter experiencing a gusty crosswind on final approach to runway 18, the pilot employed standard crosswind landing technique. Once over the threshold, power was reduced to idle and the pilot commenced the flare. During the flare, a gust of wind blew the alft…NTSB BFO85FA002Accident · 4 fatalField investigationFinal reportPiper PA-32R-301 · Salisbury, MDAfter contacting millville fss 4 times for wx info the acft departed lincoln park, NY, at 1858 EDT with destination listed on the IFR flt plan as easton, MD. En route the plt diverted to Salisbury, MD, due to wx. After being cleared forthe rwy 32 ILS the acft…NTSB NYC84LA153Accident · Minor injuriesLimited investigationFinal reportBeech B24R · Clinton, MDThe main rwy at the arpt was closed due to resurfacing. The plt was attempting a landing on rwy 31 knowing it would be a deliberate downwind landing. According to the operator of the arpt, plts were discouraged from using rwy 13 because the traffic directly…NTSB ATL84LA071Accident · No injuriesLimited investigationFinal reportPiper PA-32-260 · Indian Head, MDThe plt stated that shortly after departing dca, he encountered a small amount of rain that froze on the aircraft's windshield. He continued on to his destination and again encounter freezing rain when turning from base to final. He elected to make a…NTSB ATL83LA164Accident · Minor injuriesLimited investigationFinal reportCessna 172 · Clinton, MDWitnesses observed that the acft took off from rwy 31, began a left turn, then descend into the trees. One witness, a lineboy, stated that he heard the engine running until the acft contacted the trees. The plt received a head injury and was unable to recall…NTSB ATL83LA125Accident · No injuriesLimited investigationFinal reportRockwell 112A · Chestertown, MDThe aircraft settled back to the right of the runway during takeoff and struck an old stanchion used for runway lights. The pilot was unsure of the extent of damage and elected to re-land the aircraft. The landing gear had already been raised, so the landing…NTSB ATL83FIG03Accident · 1 fatalFinal reportCessna 172F · Hancock, MDThe aircraft collided with the top two wires of a powerline during a low altitude sight-seeing flight along the potomac river. The pilot stated he was maintaining visual contact with the ground should an emergency landing become necessary. He was staying high…NTSB ATL82FA087Accident · 4 fatalField investigationFinal reportPiper PA-28-140 · Westminster, MDThe aircraft crashed after takeoff from a 2930 ft runway with four occupants on board. The aircraft weight was not known, but was estimated to be 2334 lbs during takeoff. There was a light wind from the west and the temperature was 42 degrees fahrenheit.…