# NTSB MIA97FA049: Piper PA-30, N8220Y, Goldsboro, NC, December 28, 1996 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: December 28, 1996, 10:27 local (15:27 UTC) - Place: Goldsboro, NC - Coordinates: 35.369163, -77.970695 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=35.3692&lon=-77.9707&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed, report February 2, 1998 - Report: Approved by Office Director - NTSB case key (mKey): 38131 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=MIA97FA049 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/38131/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=38131 - Page: https://openairdocs.org/ntsb/MIA97FA049 ## Probable cause The pilot's failure to follow instrument approach procedures during numerous instrument approaches and missed approaches which resuled in a total loss of engine power on both engines due to fuel exhaustion. Factors contributing to the accident were: the pilot's failure to obtain a weather briefing prior to his departure and his lack of recent instrument flight experience. ## Sequence of events In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Loss of engine power(total) - nonmechanical, approach - preflight planning/preparation - inadequate, pilot in command (contributing factor) - weather forecast - not obtained, pilot in command (contributing factor) - ifr procedure - improper, pilot in command (cause) - lack of recent instrument time, pilot in command (contributing factor) - 2 engines - fluid,fuel - exhaustion - Forced landing, emergency descent/landing - In flight collision with object, emergency descent/landing - object - tree(s) - In flight collision with terrain/water, emergency descent/landing ## Analysis Review of transcripts revealed the pilot departed Baltimore, Maryland VFR at about 0746 to obtain fuel locally for a cross country flight to Florida. No flight plan or weather briefing had been filed or obtained prior to departure. The pilot was unable to land, encountered IFR flight conditions and filed an IFR flight plan to Florida. En route, the pilot diverted to another airport for fuel. He was cleared for an ILS approach and informed prior to beginning the approach that the weather was below minimums. The pilot made a missed approach, and informed the controller a short time later that he had lost one engine. The controller coordinated with the U.S. Air Force to allow the pilot to conduct a PAR approach, and declared the airplane an emergency. The pilot was cleared for a PAR approach. The approach was terminated by the controller, the changed to a surveillance approach which resulted in a missed approach. The pilot was vectored for another PAR approach, and it was subsequently changed to a no gyro approach. The controller informed the pilot he was too far left for a safe approach, and to climb to 1800 and fly a heading of 260 degrees. Radar contact was lost 1 mile southwest of the airport. Examination of the wreckage revealed that the fuel tanks were not ruptured and that no fuel was present. Also, a review of the pilots logbook revealed he did not meet FAA instrument recurrency requirements. ## Factual narrative HISTORY OF FLIGHT On December 28, 1996, about 1027 eastern standard time (EST), a Piper PA-30, N8220Y, registered to a private owner, operating as a 14 CFR Part 91 personal flight, crashed during an instrument approach to Seymour Johnson A.F.B. Goldsboro, North Carolina. Instrument meteorological conditions prevailed and an IFR flight plan was filed. The airplane was destroyed and the commercial pilot was fatally injured. The flight originated from Baltimore, Maryland, about 2 hours 41 minutes before the accident. Review of communication between N8220Y, Baltimore Tower, and Andrew ATCT (T-1) revealed N8220Y was cleared for a VFR takeoff at 1246 UTC (0746 EST). N8220Y contacted T-1 at 1254, reported he was level at 1200 feet, and informed the controller that he would be landing at Potomac Airpark, Maryland (VKX). The 1241 Andrew's (ADW) weather was: wind 170 at 6 knots, visibility 1 mile, measured ceiling 200 overcast, temperature 04, dewpoint 04, altimeter 30.02, and tower visibility was less than 1/2 mile. N8220Y advised T-1 at 1254:56 that he wanted to over fly the area southbound. N8220Y was issued a special VFR clearance and was asked what his flight conditions were. He informed the controller that he was in the clear, in between cloud layers, and that he could take an IFR clearance. At 1257:00, N8220Y advised the controller that he was trying to go to VKX to get gas, but if he could not get in due to weather conditions, he might have to keep flying south. T-1 advised N8220Y to continue special VFR and asked for the destination airport. N8220Y informed the controller that his destination was Florida, that he had just departed Baltimore where the weather was clear, and that he thought he could get into VKX. Review of records on file with the FAA Leesburg Automated Flight Service Station, revealed no record of a VFR flight plan or a weather briefing for N8220Y. T-1 informed N8220Y at 1258:50, that the Patuxent weather was compatible to Andrew's and Richmond's weather was worse. N8220Y requested an IFR clearance to Myrtle Beach at 1259, and was issued the IFR clearance at 1304:25 UTC (0804:25 EST). At 1416 UTC (0916 EST), N8220Y contacted Washington Center (R27) and requested the Kinston (ISO) weather. R27 states the ISO 1350 weather was: winds calm, visibility 3/16 of a mile, fog, indefinite ceiling 100. N8220Y asks R27 if the Wilmington (ILM) or the Myrtle Beach (MYR) weather is better. R27 asks N8220Y if he wanted the ILM or Grand Strand (CRE) weather and N8220Y informs him that he wants the CRE weather. The 1350 CRE weather was: wind 060 at 6 knots, visibility 4 miles, 6000 broken, temperature 12, dewpoint 12, altimeter 30.29. N8220Y informs R27 at 1417:54, that he is going to CRE, but he was thinking about stopping early to get some gas. R27 confirmed N8220Y's destination airport as CRE and issued an IFR clearance, however N8220Y states he is thinking about ISO. R27 asks N8220Y if he wants to overly ISO, and N8220Y replies, "ah let me call you back I'm checking to see what (unintelligible) what the approaches are like there." At 1428:03, N8220Y calls Seymour approach (SR) and asks for the local weather. SR informs N8220Y that ISO is IFR. N8220Y asks for the Goldsboro weather and is informed at 1430:36, that no weather is available. He is informed the Seymour Johnson, 1350 weather observation, located 6 miles south of Goldsboro, is: wind variable at 4 knots, 3/16 mile, runway 26 measured 1000 feet RVR, fog, indefinite ceiling 100 feet, and tower visibility at Seymour is 1/16 mile. N8220Y informs SR at 1436:26, "yeah a I'm , I'm running a little bit low on fuel and I don't know if I want to, want to chance it to um Grandstand, hey what's the Fayetteville look like?" SR replies at 1436:42, "23Y the uh airport that I just gave weather on, is about 30 miles uh north of you. Ah that's about the best weather I've seen for uh areas around here, and that's 1/8 mile with ground fog, and 510WP and 20Y I believe the uh, overcast layer was at two zero thousand." SR also provided the Pope Air Force Base weather. N8220Y informed the controller that he was going to Rocky Mount (RMT) and requested radar vectors. At 1438:25, SR states the weather at ISO is: winds calm, one quarter mile with fog, indefinite ceiling 100 feet, altimeter 30.33. N8220Y requested clearance to ISO and was provided vectors to the downwind and told to expect the ILS runway 5 approach. At 1441:23, SR advises Kinston Tower that N8220Y is inbound for the ILS, and is looking for gas. Kinston tower states their weather is below minimums for the approach. SR advises N8220Y of the weather conditions, informs him that if he wants to shoot the approach it is at his discretion, and verifies that he has the approach plates for the approach. N8220Y is cleared straight in for the approach at 1444:20, and is instructed to maintain 2,100 feet until on the localizer. At 1446:05, SR states, "8220Y showing you established on the localizer is that correct?" N8220Y replies, "Uh, negative. Uh this is 20Y I was shooting the ILS." SR responds, "affirmative you've been cleared for the ILS," and informs N8200Y that he is over stalls radio beacon. SR contacts Kinston tower at 1448:07 and informs them that N8200Y is 3 miles from the airport still at 1,900 feet, and that he doesn't think that N8200Y will get down on this approach. At 1449:49, SR informs Kinston tower, "he's uh, he going missed, right?" Kinston states, he hasn't said anything yet, but I think I heard him go by. SR replies, "he's passed the airport and still descending." N8220Y contacted SR at 1451:03, and is informed that the weather at Pitt Greenville (PGV), an uncontrolled airport located about 7 miles to the northeast is: wind calm, visibility 4 statue miles, 300 overcast, altimeter 30.32, and is asked if he wants to go there. N8200Y states affirmative and is provided radar vectors, and is informed to contact Washington Center (R25). At 1458:12, R25 asks N8220Y if he has the current PGV weather. N8220Y states, "ah nah plus I just lost one of my engines." R25 asks N8220Y which airport he wants to go to. N8220Y replies, " ah I got to go to the closest one I'm a little I'm comin we're comin down." R25 provides radar vectors to PGV and asks which engine is out. N8220Y replies the left engine. R25 contacts the Seymour Johnson controller (GSBZ) and asks if they can do a PAR approach, and informs them that N8220Y has lost an engine. GSBZ informs the controller, "yeah put him on a uh 200 heading and he's radar contact." GSBZ asks R25 if N8220Y has declared an emergency. R25 replies, "not as such but he lost an engine and he can't hold altitude so atc's declaring an emergency." GSBZ states, "okay we'll give him par." R25 contacts N8220Y at 1500:11 UTC (1000:11 EST), and states, "ah twin comanche two zero yankee seymour approach has got precision radar available the seymour airport is twenty three miles can you accept a vector to that airport." N8220Y replies, "okay let me do that." SR informs him that Seymour has declared him an emergency, and he is being vectored for PAR runway 26. N8220Y states at 1503:11, "Uhh, I might not make it." SR informs him to descend to 1,800 feet at pilots discretion. N8220Y replies, "Uh, you'd better let me stay at altitude as long as I can." I'm just about out of fuel. SR informs N8220Y that the descent is at pilots discretion and asks do you have an estimate in fuel sir? N8200Y replies, "I do not, no, I don't know, I'm about out. I lost one engine already." SR continued vectoring N8220Y for the approach and asked him if he was familiar with no gyro procedures, and if he has ever flown a PAR before? N8220Y replies, "affirmative." At 1506:19, SR states, "Seymour is active runway two six sir, the wind is variable at four knots, right now I'm showing the wind at one three zero at six. One fourth, one quarter mile visibility, runway 26 RVR one thousand feet with fog, indefinite ceiling ## Aircraft - Registration: [N8220Y](https://openairdocs.org/deregistered/N8220Y-2014-11-19), registration cancelled 2014-11-19, S/N 30-1348, built 1966 (OpenAirDocs) - Reported make and model: Piper PA-30 - Registry model: [Piper PA-30](https://openairdocs.org/model/piper-pa-30) (registry code 7103002) (OpenAirDocs) - Registry engine: [Lycoming IO-320 series](https://openairdocs.org/engine/lycoming-io-320-series) (registry code 41509, reciprocating) (OpenAirDocs) - Category: Airplane - Serial number: 30-1348 - Airframe hours: 3911 - Engines: Lycoming LIO-320-C1A 160 horsepower reciprocating - Damage: Destroyed - Flight: Personal, Part 91 - Registered owner: John T. Harrison III - Airworthiness certificate: Standard, Normal - Last inspection: Annual, October 1, 1996, 32 hours before - Departed: BWI, BALTIMORE, MD - Destination: GSB, NC - Flight plan: IFR ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 58; commercial; airplane ratings: multi-engine land, single-engine land; instrument ratings: airplane; medical: class 2, valid medical--w/ waivers/lim; seat: left; toxicology performed; flight hours: 2,697 total, 1,151 in this make and model, 2,580 as pilot in command, 31 in the last 90 days, 2 in the last 24 hours ## Weather - Conditions: Instrument (IMC), Day - Wind: calm - Visibility: 1 statute miles - Lowest ceiling: 100 ft - Temperature: 48 °F, dew point 48 °F - Altimeter: 30.00 inHg - Observed at: ISO, 15 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 19961228042459A](https://openairdocs.org/incident/19961228042459A), Dec 28, 1996: Piper PA30, Goldsboro, NC, Destroyed, 1 fatal. Departed into worsening weather. Got IFR clearance continued with zero IMC until low fuel. Ran out on asr at gsb. (-23) pilot departed bwi approximately 0820… ## Docket (26 files) The files NTSB released with the investigation on September 29, 1997, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=38131. 8.6 MB in all. - Supplement A (item 1, .PDF, 267 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072288&FileExtension=.PDF&FileName=Supplement%20A-Master.PDF - Supplement B (item 2, .PDF, 437 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072289&FileExtension=.PDF&FileName=Supplement%20B-Master.PDF - Supplement K (item 3, .PDF, 454 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072290&FileExtension=.PDF&FileName=Supplement%20K-Master.PDF - Witness Statements (item 4, .PDF, 92 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398944&FileExtension=.PDF&FileName=Witness%20Statements-Redacted.PDF - Transcript of Radio Communications (item 5, .PDF, 2.2 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398945&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications-Redacted.PDF - ATC Personnel Statements (item 6, .PDF, 310 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398946&FileExtension=.PDF&FileName=ATC%20Personnel%20Statements-Redacted.PDF - Maps or Charts of Accident Area, Wreckage Diagrams (item 7, .PDF, 298 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072294&FileExtension=.PDF&FileName=Maps%20or%20Charts%20of%20Accident%20Area,%20Wreckage%20Diagrams-Master.PDF - Extract Pilot Logbook (item 8, .PDF, 640 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398947&FileExtension=.PDF&FileName=Extract%20Pilot%20Logbook-Redacted.PDF - Fuel Burn Analysis and Fuel Slips (item 9, .PDF, 393 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398948&FileExtension=.PDF&FileName=Fuel%20Burn%20Analysis%20and%20Fuel%20Slips-Redacted.PDF - Extract FAA Flight Inspection (item 10, .PDF, 248 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398949&FileExtension=.PDF&FileName=Extract%20FAA%20Flight%20Inspection-Redacted.PDF - Hartzell Propeller Teardown Report (item 11, .PDF, 310 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398950&FileExtension=.PDF&FileName=Hartzell%20Propeller%20Teardown%20Report-Redacted.PDF - Extract Textron Lycoming Service Instruction (item 12, .PDF, 503 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072299&FileExtension=.PDF&FileName=Extract%20Textron%20Lycoming%20Service%20Instruction-Master.PDF - Extract Aircraft Logbooks (item 13, .PDF, 653 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398951&FileExtension=.PDF&FileName=Extract%20Aircraft%20Logbooks-Redacted.PDF - Extract Sheriff/Fire Report (item 14, .PDF, 392 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398952&FileExtension=.PDF&FileName=Extract%20Sheriff%2FFire%20Report-Redacted.PDF - Release of Aircraft Wreckage, NTSB Form 6120.15 (item 15, .PDF, 561 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398953&FileExtension=.PDF&FileName=Release%20of%20Aircraft%20Wreckage,%20NTSB%20Form%206120.15-Redacted.PDF - Statement of Party Representatives to NTSB Investigation (item 16, .PDF, 234 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398954&FileExtension=.PDF&FileName=Statement%20of%20Party%20Representatives%20to%20NTSB%20Investigation-Redacted.PDF - Toxicological Report (item 17, .PDF, 79 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40398955&FileExtension=.PDF&FileName=Toxicological%20Report-Redacted.PDF - Photo: 1 View of N8220Y at rest. (item 18, .PDF, 72 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072305&FileExtension=.PDF&FileName=Photo%3A%201%20View%20of%20N8220Y%20at%20rest.-Master.PDF - Photo: 2 Right side view of N8220Y at rest. (item 19, .PDF, 64 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072306&FileExtension=.PDF&FileName=Photo%3A%202%20Right%20side%20view%20of%20N8220Y%20at%20rest.-Master.PDF - Photo: 3 Left side view of N8220Y at rest. (item 20, .PDF, 54 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072307&FileExtension=.PDF&FileName=Photo%3A%203%20Left%20side%20view%20of%20N8220Y%20at%20rest.-Master.PDF - Photo: 4 Left rear view of N8220Y at rest. No negative available. (item 21, .PDF, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072308&FileExtension=.PDF&FileName=Photo%3A%204%20Left%20rear%20view%20of%20N8220Y%20at%20rest.%20No%20negative%20available.-Master.PDF - Photo: 5 Rear view of N8220Y at rest. (item 22, .PDF, 60 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072309&FileExtension=.PDF&FileName=Photo%3A%205%20Rear%20view%20of%20N8220Y%20at%20rest.-Master.PDF - Photo: 6 Right rear view of N8220Y at rest (item 23, .PDF, 71 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072310&FileExtension=.PDF&FileName=Photo%3A%206%20Right%20rear%20view%20of%20N8220Y%20at%20rest-Master.PDF - Photo: 7 View of N8220Y cockpit area. (item 24, .PDF, 50 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072311&FileExtension=.PDF&FileName=Photo%3A%207%20View%20of%20N8220Y%20cockpit%20area.-Master.PDF - Photo: 8 View of N8220y right propeller and engine assembly. (item 25, .PDF, 40 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072312&FileExtension=.PDF&FileName=Photo%3A%208%20View%20of%20N8220y%20right%20propeller%20and%20engine%20assembly.-Master.PDF - Photo: 9 View of N8220Y left propeller and engine assembly. No negative available. (item 26, .PDF, 48 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40072313&FileExtension=.PDF&FileName=Photo%3A%209%20View%20of%20N8220Y%20left%20propeller%20and%20engine%20assembly.%20No%20negative%20available.-Master.PDF 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.