Columbia Aircraft Mfg LC41 accident near Woburn, Massachusetts, September 15, 2018
On September 15, 2018 at about 3:03 pm local time, a 2006 Columbia Aircraft Mfg LC41, registered N2536T, was destroyed in an accident during approach (IFR final approach) near Woburn, Massachusetts (Hanscom Field). It was a personal flight under general aviation rules (Part 91). 2 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
The NTSB's probable cause their words, unchanged
The pilots' loss of control during an instrument approach in instrument meteorological conditions as a result of spatial disorientation.
Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- September 15, 2018 · about 3:03 pm local time
- Place
- Woburn, Massachusetts · Hanscom Field · map
- Type
- Accident
- Injuries
- 2 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Columbia Aircraft Mfg LC41 550FG, built 2006 · all LC41s on the register
- Registration
- N2536T · no longer on the register · serial 41594
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The instrument-rated pilot and one passenger were approaching the destination airport following an instrument flight rules cross-country flight in instrument meteorological conditions; the reported weather at the destination included ceilings between 400 and 600 ft above ground level and visibility of 2 miles in mist. The controller cleared the airplane for the instrument landing system (ILS) approach; the pilot intercepted the localizer and immediately descended below the minimum altitude he was required to maintain prior to crossing the final approach fix (FAF). The controller issued a low altitude alert as the airplane was crossing the FAF about 700 ft below the minimum altitude. The pilot responded that he was climbing; he did not report any problems or issues with his airplane to the controller. The airplane then drifted right of the localizer course and the controller advised the pilot of such, but there was no response. The airplane subsequently proceeded left of the localizer course, after which the controller issued another low altitude alert and asked the pilot if he was still on the approach. The pilot responded that he was not on the approach and that he was "pulling." During the final minute of the flight, the airplane was observed in rapid, turning climbs and descents until radar contact was lost. The airplane impacted terrain about 4.2 miles east-southeast of the airport. Accident site evidence and impact damage to the airplane were indicative of a high-velocity impact. Examination of the wreckage revealed no evidence of any preimpact mechanical anomalies, and analysis of a video doorbell that captured audio of the airplane in flight revealed an engine speed consistent with high power. The reduced visibility conditions present at the time of the accident and the high workload associated with the instrument approach were conducive to the onset of pilot spatial disorientation, and the airplane's erratic maneuvering and the high-energy impact are both consistent with the known effects of spatial disorientation. Therefore, it is likely that the pilot became spatially disoriented during the instrument approach, which resulted in a loss of airplane control.
The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.
The factual record from the NTSB's investigation tables, in plain English
What happened, in order
- Loss of control in flight during approach (IFR final approach) defining event
- Collision with terrain or object (not controlled flight into terrain) during uncontrolled descent
The NTSB's findings
- cause Personnel issues › Psychological › Perception/orientation/illusion › Spatial disorientation › Pilot
- cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › (general) › Not attained/maintained
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Contributed to outcome
- cause Environmental issues › Conditions/weather/phenomena › Ceiling/visibility/precip › Low ceiling › Effect on operation
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 1,945 hours in all; 3 in the last 90 days
- Last flight review: January 15, 2018
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: unk
- Injury: fatal
The aircraft
- Airframe total time: 1,339 hours
- Last inspection: annual inspection, December 14, 2017; 69 hours since
- Maximum gross weight: 3,600 lb
- Seats: 4
- Landing gear: fixed
- Engine: Continental TSIO-550-C (piston); 1,408 hours total
- Fire on the ground
The flight
- Departed from: FRG Farmingdale NY at 1:54 pm
- Destination: BED Bedford MA
- Flight plan: IFR
- Runway 29, 7,011 ft by 150 ft
Weather at the time
- Light: daylight
- Visibility: 2 statute miles
- Sky: overcast at 600 ft
- Temperature: 66°F (19°C), dew point 64°F (18°C)
- Altimeter: 30.20 inHg
- Observation at 3:08 pm from KBED, 5 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 1 |
Documents from the investigation the NTSB's docket: the evidence folder behind the report
28 documents, released by the NTSB on April 23, 2020. View them here, or download them; the NTSB redacts some personal details before release, and this site shows the NTSB's own titles rather than its file names.
The same docket at the NTSB · documents without a copy here are fetched from the NTSB when you open them.
Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
