FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

CEN26LA103 · Beech V35B

1 Feb 2026 · Odessa, TX, United States

Beech V35B and Piper PA28 140 · Accident: collision during takeoff/landing

Report a problem

Event

NTSB case
CEN26LA103
Event typeAccident: someone killed or seriously injured, or the aircraft substantially damaged (NTSB definition). Incident: an occurrence that affected or could have affected safety, short of that. Glossary
Accident
InvestigationHow far the investigation had got when the record was published: preliminary, ongoing, final or completed. Unknown where the source does not say. Glossary
Ongoing
API-reported fatalities
0 · all aircraft and ground
Ground fatalities
0
OperationWhat kind of flying it was, grouped by the rules it flew under: airline (US Part 121), air taxi and commuter (Part 135), general aviation (Part 91 and similar), military or government. Glossary
General aviation
WeatherVisual meteorological conditions (VMC): good enough to fly by looking outside. Instrument conditions (IMC): cloud or low visibility, flying by instruments. Glossary
Visual Meteorological Cond

Aircraft 1 · Beech V35B

Aircraft type
Beechcraft 35
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N95AB
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 48 years (built 1978)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Landing
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Collision during takeoff/landing
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Aircraft 2 · Piper PA28 140

Aircraft type
Piper PA28
Category
Airplane
RegistrationThe aircraft's tail number, such as N12345 or G-ABCD. Registrations are reissued, so the same one years apart can be a different aircraft. Glossary
N6780W
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
About 61 years (built 1965)
Flight rulesThe regulations the flight operated under: in the US, Part 91 (general aviation), Part 121 (airlines), Part 135 (air taxi and commuter) and others; for flights abroad, the NTSB's coarser commercial or non-commercial code. Glossary
Part 91: General Aviation
Phase of flightThe stage of the flight when things started to go wrong: standing, taxi, takeoff, initial climb, en route, maneuvering, approach or landing. Glossary
Taxi · to runway
Defining eventThe single coded event the NTSB judges best describes what happened (records from 2008 on). Older records name the first occurrence in the sequence instead. Glossary
Ground collision
DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
Substantial

Cause areas

No findings designated as a cause are recorded in the NTSB data yet.

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

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.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record CEN26LA103
Event ID
20260202202372
Case number
CEN26LA103
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
Source notes (4)
  • Unreviewed is an editorial label, not an investigation status. API-sourced is not report-checked or human-reviewed. Explicit event totals are used without summing aircraft injury tables; onboard allocation is withheld. Unknown values remain unknown. The operation category is mapped from the NTSB-reported FAR part and has not been reviewed.
  • Filled from the NTSB case API where the bulk record had no value: investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 10a433e55369f502702f3909a2d0dfad73fc315636a9d672e8f3634b57c8586c; retrieved 2026-09-13T18:51:48.658Z.