The U.S. aircraft register, updated daily
Accidents · NTSB CEN27LA004 · Preliminary: the investigation is not finished

Cessna 414A accident near Boerne, Texas, October 2, 2026

On October 2, 2026 at about 6:52 pm local time, a 1984 Cessna 414A, registered N1245A, was substantially damaged in an accident during takeoff near Boerne, Texas (Boerne Stage Airfield). It was a personal flight under general aviation rules (Part 91). No one was hurt; 2 people were on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

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

What the record shows

Date
October 2, 2026 · about 6:52 pm local time · cases in 2026
Place
Boerne, Texas · Boerne Stage Airfield · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 2 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft
Cessna 414A, built 1984 · all 414As on the register
Registration
N1245A · registry record · serial 414A1201
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On October 2, 2026, about 1352 central daylight time, a Cessna 414A airplane, N1245A, was destroyed when it was involved in an accident near Boerne, Texas. The pilot and pilot-rated passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 flight. According to the pilot, the airplane had just undergone its annual inspection which included the replacement of multiple engine cylinders, and this was the first flight after maintenance. During the takeoff roll from runway 17 at Boerne Stage Airfield (5C1), San Antonio, Texas, after passing 88 kts indicated airspeed, the pilot noticed that the left engine was not producing full engine power. The pilot determined that there was insufficient runway remaining to stop the airplane safely, he continued the takeoff. After the airplane lifted off from the runway, the pilot raised the landing gear and attempted to maintain control of the airplane with the maximum available engine power and an airspeed above the airplane’s minimum control speed (Vmca). The airplane struck a utility pole about 680 ft from the departure end of runway 17, subsequently igniting a fire from the right wing. The airplane impacted terrain and a post-impact fire ensued, destroying the airplane. The pilot and pilot-rated passenger egressed the airplane through the main cabin door. According to a witness, the airplane performed a static engine run on the maintenance ramp, and about 45 minutes later attempted a takeoff from runway 17. About 1,000 ft down the runway, the engine power was reduced to idle and the airplane exited the runway. During the second takeoff attempt, the witness observed the pilot apply full engine power, and about 1,000 ft down the runway, engine power was reduced to 50 percent. The witness observed the airplane become airborne and impact a powerline. The engines were recovered to a secure location for further investigation.

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. Powerplant sys/comp malf/fail during takeoff defining event

The aircraft

  • Airframe total time: 4,951.2 hours
  • Last inspection: annual inspection, October 2, 2026
  • Maximum gross weight: 7,105 lb
  • Seats: 8
  • Landing gear: retractable
  • Fire in flight and on the ground
  • Operator: Aircraft Holding Solutions LLC Trustee

The flight

  • Flight plan: VFR
  • Runway 17/3, 5,006 ft by 60 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 010° at 8 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 1,000 ft
  • Temperature: 73°F (23°C), dew point 68°F (20°C)
  • Altimeter: 30.01 inHg
  • Observation at 1:35 pm from K5C1, 1 miles away

Weather report (METAR): K5C1 021835Z AUTO 01008KT 10SM BKN010 OVC016 23/20 A3001 RMK AO1

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

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

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/CEN27LA004.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.