Mooney Aircraft CORP. M20 accident near Chuckanut, Washington, February 13, 2018
On February 13, 2018 at about 3:13 am local time, a 1979 Mooney Aircraft CORP. M20, registered N123JN, was destroyed in an accident during approach (VFR pattern final) near Chuckanut, Washington (Bellingham Intl airport). It was a personal flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).
The NTSB's probable cause their words, unchanged
The pilot's failure to maintain clearance from terrain during a visual approach in dark night visual meteorological conditions, which resulted in controlled flight into terrain.
Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- February 13, 2018 · about 3:13 am local time · cases in 2018
- Place
- Chuckanut, Washington · Bellingham Intl · cases near this airport · map
- Type
- Accident
- Injuries
- 1 person was killed.
- Weather
- visual conditions (good weather)
- Aircraft
- Mooney Aircraft CORP. M20 K, built 1979
- Registration
- N123JN · no longer on the register · serial 25-0060
- Damage
- Destroyed
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative final · quoted from the NTSB record
The private pilot was conducting a cross-country flight in dark night visual meteorological conditions. Flight track data indicated that the airplane flew direct toward the destination airport over mountainous terrain that was depicted on navigation products. As the airplane approached the destination airport, the pilot initiated a descent from 4,300 ft mean sea level (msl). About 14 miles south of the airport, the pilot requested and received clearance to conduct a straight-in approach and was instructed to report 3 miles from the runway; no further communications were received from the pilot. The airplane's groundspeed and flight track were consistent throughout the descent, and the airplane was last captured on a northwesterly heading at an altitude of 1,975 ft msl near the accident site. Evidence at the site was consistent with a wings-level, high-speed impact with treetops on a ridge at an elevation of 1,900 ft msl about 9 miles south-southeast of the destination airport. Examination of the airframe and engine revealed no evidence of mechanical malfunctions or anomalies that would have precluded normal operation. Downloaded engine data monitor information indicated that the engine was operating normally until impact. Autopsy of the pilot indicated no evidence of an incapacitating event. The airplane's consistent flight track, groundspeed, and descent rate and its high-speed, wings-level impact is consistent with controlled flight into terrain. Due to the dark night conditions and lack of ground lighting in the vicinity of the accident site, it is likely that the pilot did not see the terrain as he descended toward the destination airport.
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
- Preflight or dispatch event during prior to flight
- Controlled flight into terrain or object (CFIT) during approach (VFR pattern final) defining event
The NTSB's findings
- cause Personnel issues › Task performance › Planning/preparation › Flight planning/navigation › Pilot
- cause Personnel issues › Action/decision › Info processing/decision › Identification/recognition › Pilot
- factor Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Decision related to condition
Pilot
- Certificate: private
- Ratings: single-engine land; instrument: airplane
- Flight time: 760 hours in all; 57 in this make and model; 10 in the last 90 days; 1.2 in the last 30 days; 687.2 as pilot in command
- Last flight review: December 29, 2016
- Medical certificate: Class 3 (with waivers/limitations)
- Seat: left
- Injury: fatal
The aircraft
- Airframe total time: 4,782.2 hours
- Last inspection: 100-hour inspection, January 24, 2018; 8 hours since
- Maximum gross weight: 2,900 lb
- Seats: 4
- Landing gear: retractable
- Engine: Cont Motor TSIO-360-LB1B (piston); 1,730 hours total
The flight
- Departed from: S43 Snohomish WA at 2:51 am
- Destination: BLI Bellingham WA
- Flight plan: none
- Runway 34, 6,700 ft by 150 ft
Weather at the time
- Light: night
- Visibility: 10 statute miles
- Sky: clear
- Temperature: 30°F (-1°C), dew point 21°F (-6°C)
- Altimeter: 30.34 inHg
- Observation at 2:53 am from KBLI, 9 miles away
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 |
Photographs from the investigation 8 pictures from the NTSB's docket, as the NTSB released them
Photo 1 – N123JN Mooney M20K wreckage debris locations on a Google Earth image.
Photo 2 - Main wreckage site indicating aft fuselage and propeller.
Photo 3 - Propeller
Photo 4 - Left wing exhibiting tree strike at outer section.
Photo 5 - Vertical and left horizontal stabilizer.
Photo 6 - Cockpit section indicating engine controls and instrument panel.
Photo 7- Right separated outboard wing near initial impact site.
Photo 8 - Engine separated from the wreckage, leaning against a tree at the end of the debris field.The NTSB's photographs with the NTSB's captions, at screen size. Open a picture to see it full size or to report one that should not be shown.
Documents from the investigation the NTSB's docket: the evidence folder behind the report
13 documents, released by the NTSB on June 25, 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.
| # | Document | What it is | |
|---|---|---|---|
| 1 | NTSB Engine Data Monitor Factual Report | PDF, 3 pages · our copy | View Download |
| 2 | Engine Data Monitor - Attachment 1 | data file · our copy | Download |
| 3 | NTSB Medical Factual | PDF, 3 pages · our copy | View Download |
| 4 | Record of Conversation (Owner) | PDF, 2 pages · our copy | View Download |
| 5 | Radio Communications Transcript | PDF, 1 page · our copy | View Download |
| 6 | NTSB Examination Summary | PDF, 7 pages · our copy | View Download |
| 7 | Opsvue Flight Track Data | data file · our copy | Download |
| 8 | 72 Hour History (Family Interview and Data) | PDF, 2 pages · our copy | View Download |
| 9 | Fuel Receipt and Quality Check | PDF, 2 pages · our copy | View Download |
| 10 | Flight Log | PDF, 1 page · our copy | View Download |
| 11 | Bellingham Airport Feb 12 Inspection | PDF, 3 pages · our copy | View Download |
| 12 | Photographs | PDF, 8 pages · our copy | View Download |
| 13 | Pilot Toxicology Report | PDF, 1 page · our copy | View Download |
Other NTSB records under N123JN the same tail number, which may have belonged to a different aircraft at the time
Connections how this case links to the rest of the register
- N123JN: not on the register today · the record of its deregistration
- Engine: Cont Motor TSIO-360-LB1B 1,907 aircraft carry this series today · as the NTSB recorded it
- Bellingham International · nearest airport
- Harvey Field · departed from
- Accidents and incidents in Washington 2,713 since 1982 · 361 in the last ten years
- Washington 10,666 aircraft registered
- Other NTSB records under N123JN 1 records · the number may have belonged to another aircraft at the time
The whole map of how records connect · these connections as data: /graph/accident/ANC18FA024.json.
The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.
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 does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
