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

Piper PA-46-600TP accident near Brookshire, Texas, July 5, 2023

On July 5, 2023, a 2016 Piper PA-46-600TP, registered N600BJ, was substantially damaged in an accident during landing (landing roll) near Brookshire, Texas (Houston Executive Airport). 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
July 5, 2023 · cases in 2023
Place
Brookshire, Texas · Houston Executive Airport · 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
Piper PA-46-600TP, built 2016 · all PA-46-600TPs on the register
Registration
N600BJ · registry record · serial 4698007
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

On July 4, 2023, about 1911 central daylight time, a Piper PA-46-600TP airplane, N600BJ, was substantially damaged when it was involved in an accident at Houston Executive Airport, (TME), Brookshire, Texas. The pilot and passenger were not injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. The pilot reported that during the final approach, the airplane crossed over the runway threshold about 80 to 85 kts and touched down normally. As the nose landing gear came down, the airplane pulled to the left, so he applied right rudder to straighten it out, then the airplane suddenly veered hard to the right. The airplane did not respond to rudder pedal inputs as expected. As the airplane neared the right side of the runway, the rudder became more responsive, but the right landing gear continued into the grass. The pilot applied left rudder and turned hard to the left, crossed the runway, and exited the left side into the grass. The airplane rotated 180° from the landing direction and came to rest in the mud. The pilot and passenger exited the airplane without further incident. The black tire marks on the runway were traced back from the airplane’s final resting location, and the tire marks from the accident landing were identified. The sequence of events as indicated by the pilot matched the tires marks on the runway. The main landing gear tire marks had the tired tread pattern evident through the veer to the right. The right gear and nose gear tracks departed the right side of the runway before reentering the runway. After the airplane re-entered the runway, all three tire tracks were solid. During the veer to the left the black marks were moderate to extreme and were intermittent in a few places. A postaccident examination of the airplane revealed that the right and left gear wheels fractured from the airplane where the fork attached to the oleo strut tube. The right wing was bent upward about midspan. There was buckling damage to the lower right fuselage just aft of the wing. The nose gear remained intact and there were no anomalies noted with the gear or the steering system. There was a small impact mark on the aft face of the left side of the steering arm consistent with contacting the stop on the engine mount. The gap between the steering arm and the left and right rollers was measured in accordance with the service letter. On both sides, a 0.015” feeler gage was inserted with a little resistance. The nose gear strut had 1 1/6” of chrome visible. An Appareo Stratus 2S portable automatic dependent surveillance-broadcast (ADS-B) receiver and a multi-function display SD card were retained for data extraction and analysis.

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. Runway excursion during landing (landing roll) defining event

The aircraft

  • Seats: 6
  • Landing gear: retractable
  • Operator: Dream Sky LLC

The flight

  • Departed from: T82 Fredericksburg TX at 11:19 pm
  • Runway 36, 6,610 ft by 100 ft

Weather at the time

  • Light: daylight
  • Wind: from 110° at 5 knots
  • Visibility: 10 statute miles
  • Sky: clear
  • Temperature: 88°F (31°C), dew point 77°F (25°C)
  • Altimeter: 29.96 inHg
  • Observation at 7:15 pm from KTME

Weather report (METAR): KTME 050015Z AUTO 11005KT 10SM CLR 31/25 A2996 RMK AO2

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