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

Beech V35B and Piper PA28 accident near Odessa, Texas, February 1, 2026

On February 1, 2026 at about 8:30 pm local time, 2 aircraft, Beech V35B (N95AB) and Piper PA28 (N6780W), were involved in the same accident near Odessa, Texas. No one was hurt; 4 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
February 1, 2026 · about 8:30 pm local time · cases in 2026
Place
Odessa, Texas · cases near this airport · map
Type
Accident · collision on the ground
Injuries
No one was hurt; 4 people were on board or involved.
Weather
visual conditions (good weather)
Aircraft 1
Beech V35B, built 1978 · all V35Bs on the register
Registration
N95AB · registry record · serial D-10175
Damage
Substantial damage
Flight
Instructional flight · general aviation rules (Part 91)
Aircraft 2
Piper PA28 140, built 1965 · all PA28s on the register
Registration
N6780W · registry record · serial 28-20908
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

The NTSB's narrative for the Beech V35B preliminary · quoted from the NTSB record

On February 1, 2026, about 1430 central standard time, a Beech V35B, N9AB, and a Piper PA28-140, N6780W, were substantially damaged when they were involved in an accident near Odessa, Texas. None of the occupants, 2 in each airplane, were injured. Both airplanes were operated as Title 14 Code of Federal Regulations Part 91 personal flights. According to a statement from the pilot of N9AB, about 10 nautical miles from Odessa Airport-Schlemeyer Field (KODO), Odessa, Texas, when he had KODO in sight, he cancelled his IFR flight plan, checked the automated weather observing system (AWOS), and made an announcement on the common traffic advisory frequency (CTAF) for KODO. He reported that he flew over the airport at 4,500 feet msl, entered a left downwind for runway 11 and transmitted, “N9AB on downwind for 11.” He reported having made a normal landing on runway 11, and when he started to apply the brakes, he noticed a single-engine airplane on the runway. The pilot immediately applied full power and raised the nose of the airplane to get off the ground and avoid the other airplane. He felt the undercarriage of his airplane impact the other airplane, and subsequently he lost control of the airplane. According to the statement from the pilot of N6780W, he planned to take off from runway 20 and was monitoring the CTAF. According to the pilot the fixed-base operator had told N95AB runway 20 was the favored runway and that N95AB had acknowledged to use runway 20 to land. He heard no further radio transmissions from N95AB. He proceeded northbound toward runway 20 and had to cross two runways. He stated that before crossing each runway, “we visually cleared both directions and detected no traffic.” He then went on to say, that while crossing runway 11/29, “we again looked right, then left, and at that moment caught a brief glimpse of an approaching aircraft.” At that time, he stated his airplane was about three quarters of the way across the runway. Full braking was applied to avoid the oncoming airplane but despite braking his airplane was struck by N95AB which appeared to be attempting a landing or possible go around on runway 11. On site examination of the airplanes showed that N95AB went through the windscreen of N6780W and struck the instrument panel and other structure which resulted in substantial damage to the fuselage forward of the cockpit a-pillars. N95AB was substantially damaged and came to rest off the side of the runway with its left wing partially separated.

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 NTSB's narrative for the Piper PA28 preliminary · quoted from the NTSB record

On February 1, 2026, about 1430 central standard time, a Beech V35B, N9AB, and a Piper PA28-140, N6780W, were substantially damaged when they were involved in an accident near Odessa, Texas. None of the occupants, 2 in each airplane, were injured. Both airplanes were operated as Title 14 Code of Federal Regulations Part 91 personal flights. According to a statement from the pilot of N9AB, about 10 nautical miles from Odessa Airport-Schlemeyer Field (KODO), Odessa, Texas, when he had KODO in sight, he cancelled his IFR flight plan, checked the automated weather observing system (AWOS), and made an announcement on the common traffic advisory frequency (CTAF) for KODO. He reported that he flew over the airport at 4,500 feet msl, entered a left downwind for runway 11 and transmitted, “N9AB on downwind for 11.” He reported having made a normal landing on runway 11, and when he started to apply the brakes, he noticed a single-engine airplane on the runway. The pilot immediately applied full power and raised the nose of the airplane to get off the ground and avoid the other airplane. He felt the undercarriage of his airplane impact the other airplane, and subsequently he lost control of the airplane. According to the statement from the pilot of N6780W, he planned to take off from runway 20 and was monitoring the CTAF. According to the pilot the fixed-base operator had told N95AB runway 20 was the favored runway and that N95AB had acknowledged to use runway 20 to land. He heard no further radio transmissions from N95AB. He proceeded northbound toward runway 20 and had to cross two runways. He stated that before crossing each runway, “we visually cleared both directions and detected no traffic.” He then went on to say, that while crossing runway 11/29, “we again looked right, then left, and at that moment caught a brief glimpse of an approaching aircraft.” At that time, he stated his airplane was about three quarters of the way across the runway. Full braking was applied to avoid the oncoming airplane but despite braking his airplane was struck by N95AB which appeared to be attempting a landing or possible go around on runway 11. On site examination of the airplanes showed that N95AB went through the windscreen of N6780W and struck the instrument panel and other structure which resulted in substantial damage to the fuselage forward of the cockpit a-pillars. N95AB was substantially damaged and came to rest off the side of the runway with its left wing partially separated.

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 for the Beech V35B from the NTSB's investigation tables, in plain English

What happened, in order

  1. Collision during takeoff/land during landing defining event

The aircraft

  • Seats: 6
  • Landing gear: fixed

The flight

  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 48°F (9°C), dew point 27°F (-3°C)
  • Altimeter: 30.34 inHg
  • Observation at 2:00 pm from KODO

Weather report (METAR): METAR KODO 011953Z AUTO 00000KT 10SM CLR 09/M03 A3034 RMK AO2 SLP269 T00941028 $

Injuries

FatalSeriousMinorNone
Flight crew1
Passengers1

The factual record for the Piper PA28 from the NTSB's investigation tables, in plain English

What happened, in order

  1. Ground collision during taxi (to runway) defining event

The aircraft

  • Landing gear: fixed

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/CEN26LA103.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.