The U.S. aircraft register, updated daily
Accidents · NTSB WPR16LA028 · Final report

Beech A36 accident near Lancaster, California, November 13, 2015

On November 13, 2015 at about 3:30 am local time, a 1975 Beech A36, registered N78CR, was substantially damaged in an accident during approach (IFR initial approach) near Lancaster, California (Fox Airfield). It was an instructional flight under general aviation rules (Part 91). 2 people were seriously injured. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The flight instructor's failure to comply with published instrument approach procedures during an instrument approach in dark night, visual meteorological conditions, which resulted in impact with terrain. Contributing to the accident was the controller's failure to issue a safety alert upon noting the airplane's low altitude.

Source: NTSB aviation accident database, copy made October 5, 2026. Docket and reports at the NTSB.

What the record shows

Date
November 13, 2015 · about 3:30 am local time
Place
Lancaster, California · Fox Airfield · map
Type
Accident
Injuries
2 people were seriously injured.
Weather
visual conditions (good weather)
Aircraft
Beech A36 UNDESIGNAT, built 1975 · all A36s on the register
Registration
N78CR · no longer on the register · serial E-739
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)

The NTSB's narrative final · quoted from the NTSB record

The private pilot and flight instructor were conducting a three-leg cross-country flight in dark night, visual meteorological conditions on an instrument flight rules flight plan to an airport located in the vicinity of mountainous terrain. The pilot requested the RNAV approach, and the controller cleared the pilot direct to an intermediate fix for the approach. Three minutes later, the controller instructed the pilot to descend and maintain 7,000 ft. The airplane continued on its original heading for several minutes before turning toward the intermediate fix; the controller subsequently issued a 15o right turn to intercept the final approach course; however, the airplane turned left about 10o. The airplane continued on this heading for about 3.5 miles, when the controller cleared the airplane direct to the next fix along the approach (which should have resulted in the airplane turning left), with an altitude restriction at or above 7,000 ft until reaching the fix. The pilot incorrectly read back the fix, and the airplane turned right, likely toward the intermediate fix to which he had been previously cleared. The controller did not correct the pilot's readback of this clearance. Several minutes later, at 7,250 ft, the pilot reported the intermediate fix inbound. The controller did not hear this transmission because he was on a landline with the tower controller at the time. Rather than turning onto the approach course, the airplane continued a southerly heading through the fix and the final approach course, and several minutes later, the pilot again asked the controller for an approach clearance. The controller cleared the airplane for the approach with no additional information. The airplane was not established on the published approach at that time, and as the airplane turned north/northwest to intercept the final approach course, it was well below the published minimum altitude for that segment of the approach. The controller subsequently asked the pilot if he had the terrain in sight, and the pilot first responded that he had the airport in sight. When asked again if he had the terrain in sight, the pilot responded that he did. The controller then instructed the pilot to contact the airport tower controller. At that time the airplane was at an altitude of 5,325 ft; the minimum altitude for that segment of the approach was 6,400 ft. The airplane continued to descend along the final approach course; the last recorded radar position of the airplane was at an altitude of 4,150 ft and nearly coincident with the accident site. Both pilots reported to first responders that they thought they were flying too high, but instead they were too low, and that they flew into terrain. Both pilots also reported that there were no mechanical malfunctions of the airplane. The circumstances of the accident are consistent with the flight instructor's failure to comply with the minimum published altitudes for the approach, which would have ensured terrain clearance. Although the controller likely recognized the airplane's low altitude, and as a result asked if they had the terrain in sight, it is likely that, had he issued a safety alert and instructed the pilots to climb, the collision with terrain may have been averted.

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

  1. Controlled flight into terrain or object (CFIT) during approach (IFR initial approach) defining event

The NTSB's findings

  • cause Personnel issues › Action/decision › Action › Lack of action › Pilot
  • cause Aircraft › Aircraft oper/perf/capability › Performance/control parameters › Altitude › Not attained/maintained
  • factor Environmental issues › Conditions/weather/phenomena › Light condition › Dark › Effect on personnel
  • factor Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › Instructor/check pilot
  • factor Personnel issues › Psychological › Attention/monitoring › Task monitoring/vigilance › ATC personnel
  • factor Personnel issues › Action/decision › Action › Incorrect action selection › ATC personnel

Pilot

  • Certificate: private
  • Ratings: single-engine land
  • Flight time: 340 hours in all; 65 in this make and model; 17 in the last 90 days; 17 in the last 30 days; 340 as pilot in command
  • Last flight review: January 24, 2015
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: left
  • Injury: minor injuries

Flight instructor

  • Certificate: flight instructor, commercial pilot
  • Ratings: multi-engine land; single-engine land; instructor: airplane single-engine; instructor: instrument airplane; instrument: airplane
  • Flight time: 6,900 hours in all; 27 in this make and model; 100 in the last 90 days; 34 in the last 30 days; 6,590 as pilot in command; 2,073 on instruments
  • Last flight review: August 8, 2015
  • Medical certificate: Class 3 (with waivers/limitations)
  • Seat: rgt
  • Injury: serious injuries

The aircraft

  • Airframe total time: 6,998 hours
  • Last inspection: annual inspection, March 16, 2015; 27 hours since
  • Maximum gross weight: 3,651 lb
  • Seats: 6
  • Landing gear: retractable
  • Engine: Continental IO-520-BB (piston); 1,280 hours total

The flight

  • Departed from: KBFL Bakersfield CA at 3:00 am
  • Destination: KWJF Lancaster CA
  • Flight plan: IFR
  • Runway 6, 7,201 ft by 150 ft
  • A second pilot was aboard

Weather at the time

  • Light: night
  • Wind: from 300° at 3 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 39°F (4°C), dew point 12°F (-11°C)
  • Altimeter: 30.13 inHg
  • Observation at 3:56 am from KWJF, 15 miles away

Injuries

FatalSeriousMinorNone
Flight crew2

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), has not been read from the NTSB for this case yet; the list appears here once it has. Open the docket at the NTSB.

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.