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

Hawker T Mk 7A accident near Pittston, Pennsylvania, July 22, 2003

On July 22, 2003 at about 12:59 pm local time, a Hawker T Mk 7A, registered UNREG, was destroyed in an accident near Pittston, Pennsylvania (Wilkes-Barre/Scranton Arpt airport). It was a positioning flight under general aviation rules (Part 91). 1 person was killed. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The pilot's failure to abort the takeoff, after the engine experienced a partial power loss for undetermined reasons. Factors were the pilot's improper preflight planning by his failure to determine if the airplane was airworthy, and the operators inadequate maintenance on the airplane, the use of non-certificated mechanics to perform the work on the airplane, and his failure to ensure the airplane met the minimum standards necessary for flight.

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

What the record shows

Date
July 22, 2003 · about 12:59 pm local time
Place
Pittston, Pennsylvania · Wilkes-Barre/Scranton Arpt · map
Type
Accident
Injuries
1 person was killed.
Weather
visual conditions (good weather)
Aircraft
Hawker T Mk 7A
Registration
UNREG · no longer on the register · serial 41H695333
Damage
Destroyed
Flight
Positioning flight · general aviation rules (Part 91)

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

The pilot of the Hawker Hunter performed three aborted takeoffs in the 4 days that preceded the accident flight. A witness reported that each time, the pilot reported the brakes were dragging. The pilot also reported the engine was running "cool", but was OK. On the fourth attempted takeoff, witnesses reported the engine did not sound as loud as they expected and the airplane appeared slow. At the end of the 7,500 foot runway, the airplane abruptly pitched up, became airborne with wings rocking from side to side, and then disappeared below the level of the runway. The airplane impacted in an open field, below the level of the runway, in a nose high attitude and traveled into a wooded area. The pilot initiated ejection; however, the canopy did not separate from the airplane and the seat went through it. Three of the four canopy locks were found still locked. Water was found in the fuel filter. The airplane had received a replacement engine a month earlier, but was not signed off as airworthy. When the engine was ground run after the change, it was found to not meet two separate acceleration tests. The owner reported the maintenance records were on the airplane; however, none were found, and he never produced any documents to determine the airworthiness of the airplane. The last known annual inspection occurred 13 months prior to the flight. The airplane had been in non-preserved storage for over a year. The owner had de-registered the airplane with the FAA, with the intent of moving it to Canada; however, he had not applied for Canadian registration. After each aborted takeoff, the airplane was worked on by two non-certificated mechanics.

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

Pilot

  • Certificate: commercial pilot
  • Ratings: single-engine land; instrument: airplane
  • Flight time: 6,574 hours in all; 235 in this make and model; 6,574 as pilot in command
  • Medical certificate: Class 2 (valid medical--w/ waivers/lim.)
  • Seat: left
  • Injury: fatal

The aircraft

  • Airframe total time: 4,789 hours
  • Last inspection: annual inspection, June 1, 2002; 0 hours since
  • Maximum gross weight: 25,000 lb
  • Seats: 2
  • Landing gear: retractable
  • Engine: Rolls-Royce Avon Mark 122 (turbojet); 0 hours total
  • Fire on the ground

The flight

  • Departed from: AVP Avoca PA at 12:59 pm
  • Destination: BTV Burlington VT
  • Flight plan: none
  • Runway 22, 7,501 ft by 150 ft

Weather at the time

  • Light: daylight
  • Wind: from 230° at 5 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 10,000 ft; a few clouds at 800 ft
  • Temperature: 68°F (20°C), dew point 64°F (18°C)
  • Altimeter: 29.80 inHg
  • Observation at 12:54 pm from AVP, 1 miles away

Injuries

FatalSeriousMinorNone
Crew1

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.

Other NTSB records under UNREG the same tail number, which may have belonged to a different aircraft at the time

2026-07-07CEN26LA246 · accident near Hooker, OK · substantial damage · minor injuries
2026-02-28CEN26LA131 · accident near Van Burensburg, IL · substantial damage · no injuries
2025-10-13ERA26LA017 · accident near Gaffney, SC · substantial damage · serious injuries
2025-09-27CEN25LA397 · accident near Harvard, IL · substantial damage · no injuries
2025-09-12CEN25LA385 · accident near Rossville, IN · substantial damage · serious injuries
2025-07-07CEN25LA242 · incident near Ingram, TX · minor damage · no injuries
2025-06-18DCA25WA305 · accident near N/A · serious injuries
2025-05-01OPS25LA034 · incident near Washington, DC
2025-04-11CEN25LA155 · accident near Brady, TX · substantial damage · serious injuries
2025-01-30DCA25MA108 · accident near Washington, DC · destroyed · fatal

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.