Foster John Glasair III accident near Oxford, CT
On January 13, 2010, a Foster John Glasair III (airplane) was involved in an accident near Oxford, CT. 1 person died. Damage to the aircraft: substantial.
- Date
- January 13, 2010
- Place
- Oxford, CT
- Aircraft
- Foster John Glasair III · Airplane
- Injuries
- 1 fatal, 0 serious, 0 minor
- Damage
- Substantial
- Position
- 41.479°N, 73.135°W
- NTSB ID
- 20100114X81633
Official records · ERA10LA113
- Public docket: reports, statements and exhibits from the investigation
Air traffic control records
- Electronic Data Recording Instruments- Specialist's Factual Report of Investigation: Document (PDF), on ntsb.gov
- Addendum 1 Electronic Data Recording Instruments- Engine Monitor Data: Document (CSV), on ntsb.gov
- Transcript of Radio Communications; ATC Transcript.: Transcript (PDF), on ntsb.gov
- ATC Weather Information: Document (PDF), on ntsb.gov
NTSB summary
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 an
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.
More accidents in CT
- Boeing B17, Oct 2, 2019
- Cessna 560, Sep 2, 2021
- Cessna 182Q, Jun 27, 2005
- Mooney M20C, Sep 16, 2017
- Luscombe 8, Apr 18, 2017
Browse: Connecticut
Source: NTSB aviation accident database (US government, public domain). Findings may be preliminary or later revised by the NTSB. Not a complete global record.
