# NTSB IAD97FA001: Piper PA-32-300, N2881W, Brandywine, MD, October 2, 1996 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: October 2, 1996, 11:12 local (15:12 UTC) - Place: Brandywine, MD - Coordinates: 38.689517, -76.850715 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=38.6895&lon=-76.8507&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 3 fatal - Status: Completed, report March 31, 1998 - Report: Approved by Office Director - Safety recommendations: Yes - NTSB case key (mKey): 28118 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=IAD97FA001 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/28118/pdf - Page: https://openairdocs.org/ntsb/IAD97FA001 ## Probable cause The pilots failure to maintain his assigned altitude in IFR conditions. A related factor was the failure of the radar controller to prevent the descent of N2881W to an altitude below the minimum vectoring altitude. Additionally, the controller's failure to issue a safety alert after the MSAW issued 4 warnings in the radar room. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - In flight collision with terrain/water, circling (ifr) - weather condition - low ceiling (contributing factor) - altitude/clearance - not maintained, pilot in command (cause) - approach/departure control service - inattentive, atc personnel(dep/apch) (contributing factor) ## Analysis The pilot was receiving vectors from air traffic control for a visual approach to Hyde Field Airport. The pilot was in instrument meteorological conditions and attempting to acquire visual meteorological conditions to conduct the landing. The last assigned altitude given to the pilot by ATC was 1600 feet, which was the minimum vectoring altitude for that area. The pilot radioed ATC and informed them that he was descending to 1000 feet. ATC did not respond to the pilot's radio call. The airplane descended to 1000 feet, circled 360 degrees and had almost completed a second circle when it was lost off radar. The last recorded altitude was 800 feet, the airplane subsequently descended into the terrain with no warning provided by ATC. ## Factual narrative HISTORY OF FLIGHT On October 2, 1996, at about 1112 EDT, N2881W, a Piper PA-32-300, was destroyed when it impacted trees in a heavily wooded area near Brandywine, Maryland, approximately 3 miles south of the Washington Executive/Hyde airport, his intended destination in Clinton, Maryland. The pilot and two passengers received fatal injuries. The flight had originated in Somerville, New Jersey about 0900. Instrument meteorological conditions existed and an instrument flight rules flight plan had been filed. The flight was conducted under the provisions of 14 CFR Part 91. The pilot was receiving air traffic control (ATC) services from the radar controller at the Washington National terminal radar approach control (TRACON). At 0638, the pilot contacted Millville Flight Service Station (FSS) via telephone for a weather briefing and to file his flight plan. The briefer informed the pilot that IFR conditions existed for his entire route of flight and that the weather at Andrews Air Force Base was: "few clouds at two thousand feet, broken ceilings at two thousand five hundred, overcast at four thousand five hundred and visibility seven in light drizzle and their surface wind zero five zero at four." The pilot filed his flight plan using Baltimore Martin as his alternate. At the time of the accident the pilot was receiving vectors from ATC in an attempt to find Visual meteorological conditions (VFR) so the pilot could land at Hyde Airport. The last assigned altitude given to the pilot by ATC was 1600 feet, which is the minimum vectoring altitude for that area. The pilot radioed ATC and informed them that he was descending to 1000 feet. ATC did not respond to the pilots' radio call. The airplane descended to 1000 feet, and according to radar data the airplane circled 360 degrees and had almost completed a second circle when contact was lost. The last Radar hit showed the airplane at 800 feet. PERSONNEL INFORMATION The pilot held a Commercial certificate for airplane single engine land, Multi-engine land, and instrument airplane. The pilot had about 1,732 civilian flight hours in all aircraft and 450 hours in type. The pilots' most recent third class medical certificate was issued on September 14, 1996. AIRCRAFT INFORMATION The Piper PA-32-300, S/N 32-7940180, was manufactured and certificated in 1979. FAA records indicate that the aircraft was registered to the current owner on February 24, 1984. The aircraft's maintenance records indicated that the most recent inspection was an Annual Inspection, which was dated April 1, 1996. The aircraft had accumulated a total time of about 1,290 hours at the time of the accident. A review of the aircraft maintenance logbooks revealed no recorded discrepancies. METEOROLOGICAL INFORMATION Instrument Meteorological conditions existed at the time of the accident. A review of automatic terminal information system (ATIS) broadcast from Washington National indicated the following: Broadcast from 1059 to 1121 EDT "Washington National Airport information golf one four five eight zulu wind calm visibility one and one fourth light drizzle mist ceiling seven hundred overcast temperature one eight dewpoint one seven altimeter three zero two seven I-L-S runway three six approach in use landing runways three three six and three three the last six hundred feet of runway three three is not visible from the tower Fahrenheit temperature's six four pilots are reminded of the two prohibited areas north of the airport advise on initial contact you have golf". WRECKAGE EXAMINATION/DOCUMENTATION On October 3, 1996, an on scene examination was conducted with representatives from the Federal Aviation Administration, the New Piper Aircraft company, and Textron Lycoming. Examination of the wreckage path revealed broken and cut tree limbs between one to two inches in diameter along the first 100 feet of the wreckage path. The wreckage continued another 10 feet and impacted a large hickory tree. Fragments of propeller spinner screws, prop hub and engine sump were found imbedded in the tree trunk. The aircraft then continued another 175 feet and major sections of the airframe structure and engine became displaced by subsequent tree contacts. The total length of the wreckage path was about 285 feet. Aviation fuel was found throughout portions of the airframe and engine components/systems. An examination of the engine assembly disclosed the following: The No. 1 cylinder and one propeller blade were found separated. The front section of the engine case was destroyed exposing the crankshaft and camshaft. Repeated searches in the area through thick undergrowth recovered all engine components except the right magneto. Of the two mounting lugs for the right magneto, one was sheared off, the other was found tight and secure. Multiple crankcase fractures limited crankshaft rotation. Partial disassembly of the engine included inspection and testing of individual components of the air induction, fuel injection, ignition, lubrication and exhaust systems, with no pre-impact anomalies noted. Inspection of the spark plugs revealed clean burning combustion deposits consistent with normal operation. Examination of the propeller and spinner assemblies disclosed that one blade was torn from the hub and was bent moderately aft. Both blades had leading edge damage and chordwise scratches. The opposite blade remained in the hub, torsional bending was noted, and was bent forward at the tip. The internal pitch change mechanism of both blades was found broken. AIR TRAFFIC CONTROL INFORMATION The following is a brief summary of some of the radio transmissions that occurred between the pilot and Air Traffic Control near the time of the accident. For a complete transcript see the attached Air Traffic Control Factual Report of Investigation. At 1105:15, the controller instructed, "eight one whiskey maintain one thousand six hundred turn right heading two one zero". The pilot replied, "two one zero and sixteen hundred". At 1105:33, the controller advised, "november eight one whiskey I'm gonna bring you I'll have a right turn for you back towards the airport in about three more miles." At 1105:38, the pilot replied, "eight one whiskey three more miles right turn". At 1105:18, the controller transmitted, "november eight one whiskey turn right heading zero four zero". The pilot acknowledged the transmission. At 1107:18, the controller transmitted, "november eight one whiskey you should be in a right a right turn to zero four zero". The pilot then advised that he would make a right turn to the heading. At 1107:27, the controller replied, no keep the heading eight one whiskey make a left turn now cause you're already doing it go left a left turn for three three zero". The pilot repeated the heading. At 1108:10, the pilot advised, "eight one whiskey's coming around to three three zero sixteen hundred feet one point six". At 1108:15, the controller replied, thank you I'll have a turn for you in a moment to go northbound for eight ah eight one whiskey". The pilot requested that the transmission be repeated. At 1108:24, the controller transmitted, "eight one whiskey fly heading three four zero the airport twelve o'clock (two) miles". At 1108:30, the pilot replied, "three four zero four miles and ah I'll go down to a thousand and see if I can get it if not I'll go to my alternate which is Baltimore Martin". At 1109:26, the controller inquired, "eight one whiskey what's your heading at this time". At 1109:30, the pilot replied, "eight one whiskey on a one four----.2" At 1109:36, the pilot advised, "(unintelligible) sir I ah went down to a ----". At 1109:41, the controller replied, "okay eight one whiskey we're not going to be able to get you into that airport climb and maintain three thousand fly heading one eight zero". At 1109:49, the pilot transmitted, "going to Baltimore Marti ## Aircraft - Registration: [N2881W](https://openairdocs.org/deregistered/N2881W-1997-02-28), registration cancelled 1997-02-28, S/N 327940180 (OpenAirDocs) - Reported make and model: Piper PA-32-300 - Registry model: [Piper PA-32-300](https://openairdocs.org/model/piper-pa-32-300) (registry code 7103212) (OpenAirDocs) - Category: Airplane - Serial number: 32-7940180 - Airframe hours: 1290 - Engines: Lycoming IO-540-K1G5 300 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: Leila Schott - Airworthiness certificate: Standard, Normal - Last inspection: Annual, April 1, 1996 - Departed: N52, SOMERVILLE, NJ - Destination: W32, CLINTON, MD - Flight plan: IFR - Airport: W32, Washington Exec-Hyde Arpt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 71; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 3, valid medical--w/ waivers/lim; seat: left; toxicology performed; flight hours: 1,732 total, 450 in this make and model, 1,732 as pilot in command, 5 in the last 90 days, 3 in the last 30 days, 2 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Day - Wind: 30° at 2 knots - Visibility: 2 statute miles - Lowest ceiling: 1,000 ft overcast - Temperature: 63 °F, dew point 61 °F - Altimeter: 30.00 inHg - Observed at: DCA, 3 nm away ## FAA reports on this event (1) The FAA's own accident and incident reports, matched to the aircraft by N-number and date (OpenAirDocs). - [Accident 19961002030789A](https://openairdocs.org/incident/19961002030789A), Oct 2, 1996: Piper PA32300, Clinton, MD, Destroyed, 3 fatal. On approach to airport when radio and radar contact lost. Crashed. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.