# NTSB ERA10LA113: Foster John Glasair III, N540WF, Oxford, CT, January 13, 2010 - Type: NTSB accident investigation - Classification: Accident · Fatal · Limited investigation · Final report - Date: January 13, 2010, 16:56 local (21:56 UTC) - Place: Oxford, CT - Coordinates: 41.47861, -73.135276 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=41.4786&lon=-73.1353&mi=10 - Phase of flight: [Approach](https://openairdocs.org/ntsb-phases/500) (OpenAirDocs' grouping) - Defining event: [Approach-VFR pattern final: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) - Highest injury: Fatal - Injuries: 1 fatal - Status: Completed, report October 6, 2011 - Report: Approved by Office Director - NTSB office: Eastern Region Aviation - Parties: FAA/FSDO - NTSB case key (mKey): 75266 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=ERA10LA113 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/75266/pdf - NTSB docket: https://data.ntsb.gov/Docket?ProjectID=75266 - Page: https://openairdocs.org/ntsb/ERA10LA113 ## Probable cause The pilot's failure to maintain a proper approach path during visual conditions at dusk, which resulted in an in-flight collision with power lines. ## Findings NTSB's coded findings; those marked are part of the probable cause. - [Performance/control parameters: descent/approach/glide path](https://openairdocs.org/ntsb-findings/01062040): Aircraft › Aircraft oper/perf/capability · Not attained/maintained (probable cause); cases with it: [Foster John GLASAIR III, 1 case](https://openairdocs.org/ntsb-findings/01062040/cases.md?model=056249C), [All aircraft, 809 cases](https://openairdocs.org/ntsb-findings/01062040/cases.md) - [Experience/qualifications: recent experience](https://openairdocs.org/ntsb-findings/02031035): Personnel issues › Experience/knowledge · Pilot; cases with it: [Foster John GLASAIR III, 1 case](https://openairdocs.org/ntsb-findings/02031035/cases.md?model=056249C), [All aircraft, 76 cases](https://openairdocs.org/ntsb-findings/02031035/cases.md) ## Sequence of events The events NTSB coded, in order, by phase of flight. The defining event best describes what happened. - [Approach-VFR pattern final: Altitude deviation](https://openairdocs.org/ntsb-events/282); cases with it: [Foster John GLASAIR III, 1 case](https://openairdocs.org/ntsb-events/282/sequence.md?model=056249C), [All aircraft, 104 cases](https://openairdocs.org/ntsb-events/282/sequence.md) - [Approach-VFR pattern final: Collision during takeoff/land](https://openairdocs.org/ntsb-events/490) (defining event); cases with it: [Foster John GLASAIR III, 1 case](https://openairdocs.org/ntsb-events/490/sequence.md?model=056249C), [All aircraft, 1,309 cases](https://openairdocs.org/ntsb-events/490/sequence.md) - [Approach-VFR pattern final: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Foster John GLASAIR III, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=056249C), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) - [Uncontrolled descent: Collision with terr/obj (non-CFIT) ](https://openairdocs.org/ntsb-events/470); cases with it: [Foster John GLASAIR III, 1 case](https://openairdocs.org/ntsb-events/470/sequence.md?model=056249C), [All aircraft, 10,189 cases](https://openairdocs.org/ntsb-events/470/sequence.md) ## Analysis During a visual approach, at dusk, to a runway with an operating precision approach path indicator (PAPI), the pilot flew well below the approach path and collided with power lines on the final approach leg of the traffic pattern. The pilot had accumulated a total of 7.2 hours of night flight experience and his most recent night flight was more than 4 years prior to the accident. The accident occurred 11 minutes after sunset and 20 minutes before the end of civil twilight. The darker lighting conditions would have required the pilot to rely more on approach aids such as the PAPI lights. Examination of the wreckage and data recovered from an engine instrument system did not reveal any preimpact mechanical malfunctions of the airplane. ## Factual narrative On January 13, 2010, at 1656 eastern standard time, an experimental, amateur-built, Foster Glasair III, N540WF, received substantial damage when it collided with a high tension power line, while on final approach to runway 36 at Waterbury-Oxford Airport (OXC), Oxford, Connecticut. The certificated private pilot was killed. Visual meteorological conditions prevailed and a visual flight rules (VFR) flight plan was filed for the personal flight. The airplane was registered to and operated by the private pilot under the provisions of 14 Code of Federal Regulations Part 91. The flight originated from the Montgomery County Airport (GAI) Gaithersburg, Maryland, about 1515. According to information from the Federal Aviation Administration (FAA), OXC air traffic control tower, at 1650, the pilot established radio contact with the tower. The pilot reported his position as 15 miles west of the airport. The tower controller instructed the pilot to report when he was "midfield downwind" for runway 36, which the pilot acknowledged. At 1653, the controller queried the pilot as to his current position. The pilot responded that he was 8 miles west of the airport. At 1654, the controller informed the pilot that he believed he had him in sight and instructed him to proceed to and report a 2-mile left base, which the pilot acknowledged. The controller then provided the pilot with information regarding another airplane in the traffic pattern, on a left downwind leg for runway 36, and informed the pilot that he will be following that airplane. At 1656, the controller cleared the pilot to land and informed him that the airplane ahead was on a short final leg and no traffic factor, which the pilot acknowledged. No further communications were received from the accident airplane. Examination of the accident site by an FAA inspector found that the airplane had impacted a high tension power line about 200 feet below the precision approach path indicator (PAPI) lights for runway 36. After contact with the power line, the airplane traveled approximately 400 feet, before striking the ground near the approach end of the runway. Examination of the wreckage revealed that the landing gear selector switch was in the down position, but bent. Saw-tooth markings were observed on both main landing gear, consistent with wire strike markings. No saw-tooth markings were observed on the nose gear. Both main landing gear tires remained inflated. There were scuff marks observed on the outside of the left main tire, and on the tread of the right main tire. The flap handle was observed between the first and second extended position, and the switch was broken. Examination of the engine found it intact, facing south, with the nose gear assembly attached, but buckled underneath. There was no indication of cylinder failure and the push rods remained intact. The firewall remained attached to the engine. The propeller separated from the engine. There was leading edge damage to the propeller blades,with 1/2-inch gouges near the tips of the blades. At the conclusion of the engine and airframe examination, no evidence of any preimpact mechanical failure or malfunction was found. The pilot, age 50, held a private pilot certificate, with a rating for airplane single-engine land, which was issued on August 21, 2005. His most recent FAA third-class airman medical certificate was issued on December 24, 2008, with no restrictions. A review of the pilot's logbook by the FAA inspector indicated that he had accumulated a total flight experience in all aircraft of 278 hours. Of the total experience, 3.6 hours were in flown during the 90 days preceding the accident. The pilot had accumulated 28.7 hours in the Glasair III and his most recent biannual flight review was recorded on July 9, 2009. Lastly, the pilot had accumulated a total night experience of 7.2 hours and his last night flight was completed on September 11, 2005. The airplane was a two-seat, low-wing, retractable-gear, single-engine airplane, serial number 001, airworthiness date March 1, 2008. It was powered by a Lycoming IO-540-KIA5, 300-horsepower engine. The aircraft logbook was not recovered and no determination could be made of its most recent condition inspection or total hours of operation. A review of recorded weather data from the OXC automated weather observation station, elevation 726 feet, revealed at 1645, conditions were winds calm, visibility 10 statute miles, sky clear, temperature minus 3 degrees Celsius, dew point temperature minus 11 degrees Celsius, and altimeter 30.12 inches of mercury. Sunset was recorded at 1645 with a waning crescent moon; of which, 2 percent of the moon's visible disc was illuminated. The end of civil twilight was recorded at 1716. An autopsy was performed on the pilot on January 14, 2010, by the Office of the Chief Medical Examiner, State of Connecticut, Farmington, Connecticut. Forensic toxicology was performed on specimens from the pilot by the FAA Bioaeronautical Sciences Research Laboratory, Oklahoma City, Oklahoma. The toxicology report indicated that there was no carbon monoxide or cyanide detected in blood, no ethanol detected in vitreous, and no drugs detected in urine. The airplane was equipped with several electronic devices, including a Garmin GPSMAP 496 global positioning system receiver, an Electronic International MVP-50 engine data cockpit display, an altitude encoder, and a CD ignition system. Neither the altitude encoder nor the CD ignition system recorded any data. The Garmin GPSMAP 496 recorded data that was successfully downloaded and plotted. The plotted data revealed the flight path of the airplane, descending below the approach path, while on final approach to runway 36. The Electronic International MVP-50 also provided usable data for the investigation, which included data consistent with continuous engine operation to the impact. Shortly after the accident on January 26, 2010, the FAA performed a flight test of the PAPIglide slope to runway 36. The test results were satisfactory. ## Aircraft - Registration: [N540WF](https://openairdocs.org/deregistered/N540WF-2018-01-24), registration cancelled 2018-01-24, S/N 001, built 2008 (OpenAirDocs) - Reported make and model: Foster John Glasair III - Registry model: [Foster John GLASAIR III](https://openairdocs.org/model/foster-john-glasair-iii) (registry code 056249C) (OpenAirDocs) - Registry engine: [Lycoming IO-540 series](https://openairdocs.org/engine/lycoming-io-540-series) (registry code 41585, reciprocating) (OpenAirDocs) - Category: Airplane, amateur-built - Serial number: 001 - Engines: Lycoming IO-540-K1H5 300 horsepower reciprocating - Damage: Substantial damage - Flight: Personal, Part 91 - Operator: Foster John W - Registered owner: Foster John W - Airworthiness certificate: Special, Experimental (Special) - Departed: GAI, Gaithersburg, MD - Destination: OXC, Oxford, CT - Flight plan: VFR - Airport: OXC, Waterbury-Oxford Arpt, runway 36, 5,800 × 100 ft, asphalt ## Flight crew As NTSB recorded them. NTSB leaves out names. - Pilot; age 50; injuries: fatal; private; airplane ratings: single-engine land; medical: class 3, without waivers/limitations; last flight review July 9, 2009; seat: front; toxicology performed; flight hours: 279 total, 29 in this make and model, 4 in the last 90 days, 1 in the last 24 hours ## Weather - Conditions: Visual (VMC), Dusk - Visibility: 10 statute miles - Lowest ceiling: none - Temperature: 27 °F, dew point 12 °F - Altimeter: 30.12 inHg - Observed at: OXC ## 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 20100113026189A](https://openairdocs.org/incident/20100113026189A), Jan 13, 2010: Foster John GLASAIR III, Oxford, CT, Destroyed, 1 fatal. Pilot impacted steel cable over high tension wires 1/4 mi short of the approach end of runway 36 at oxc airport. Aircraft impacted the ground and bounced 144… ## Docket (12 files) The files NTSB released with the investigation on August 19, 2011, on NTSB's docket system: https://data.ntsb.gov/Docket?ProjectID=75266. 3.6 MB in all. - Electronic Data Recording Instruments- Specialist's Factual Report of Investigation (item 1, .PDF, 1.0 MB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40345054&FileExtension=.PDF&FileName=Electronic%20Data%20Recording%20Instruments-%20Specialist%27s%20Factual%20Report%20of%20Investigation-Master.PDF - Addendum 1 Electronic Data Recording Instruments- Engine Monitor Data (item 2, .CSV, 215 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40343066&FileExtension=.csv&FileName=Addendum%201%20Electronic%20Data%20Recording%20Instruments-%20Engine%20Monitor%20Data-Master.csv - Reports from Federal Agencies; FAA Inspectors Statement. (item 3, .PDF, 57 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351488&FileExtension=.PDF&FileName=Reports%20from%20Federal%20Agencies;%20FAA%20Inspectors%20Statement.-Redacted.PDF - Transcript of Radio Communications; ATC Transcript. (item 4, .PDF, 89 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351443&FileExtension=.PDF&FileName=Transcript%20of%20Radio%20Communications;%20ATC%20Transcript.%20-Redacted.PDF - ATC Weather Information (item 5, .PDF, 67 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351447&FileExtension=.PDF&FileName=ATC%20Weather%20Information-Redacted.PDF - Weather Reports and Records; Weather Briefing. (item 6, .PDF, 69 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351446&FileExtension=.PDF&FileName=Weather%20Reports%20and%20Records;%20Weather%20Briefing.-Redacted.PDF - Other Pertinent Forms and Reports, Airport Information and diagram. (item 7, .PDF, 21 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351162&FileExtension=.PDF&FileName=Other%20Pertinent%20Forms%20and%20Reports,%20Airport%20Information%20and%20diagram.-Master.PDF - Other pertinent forms and reports; FAA PAPI Flight Check (item 8, .PDF, 849 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351168&FileExtension=.PDF&FileName=Other%20pertinent%20forms%20and%20reports;%20FAA%20PAPI%20Flight%20Check-Master.PDF - Reports from State Agencies; Connecticut DOT Report (item 9, .PDF, 219 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351273&FileExtension=.PDF&FileName=Reports%20from%20State%20Agencies;%20Connecticut%20DOT%20Report-Redacted.PDF - Sun And Moon Data (item 10, .PDF, 10 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351456&FileExtension=.PDF&FileName=Sun%20And%20Moon%20Data-Master.PDF - Toxicological Report (item 11, .PDF, 46 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351444&FileExtension=.PDF&FileName=Toxicological%20Report-Redacted.PDF - Photo: Wire Strike Markings on Landing Gear (Photo Courtesy of FAA) (item 12, .PDF, 879 KB): https://data.ntsb.gov/Docket/Document/docBLOB?ID=40351276&FileExtension=.PDF&FileName=Photo%3A%20%20Wire%20Strike%20Markings%20on%20Landing%20Gear%20(Photo%20Courtesy%20of%20FAA)-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.