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

Beech 23 accident near Selinsgrove, Pennsylvania, April 3, 2000

On April 3, 2000 at about 9:40 pm local time, a Beech 23, registered N1923L, was substantially damaged in an accident near Selinsgrove, Pennsylvania (Selinsgrove airport). It was a personal flight under general aviation rules (Part 91). No one was hurt; 1 person was on board or involved. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The student pilot's inadequate correction for torque, which resulted in a loss of directional control of the airplane.

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

What the record shows

Date
April 3, 2000 · about 9:40 pm local time · cases in 2000
Place
Selinsgrove, Pennsylvania · Selinsgrove · cases near this airport · map
Type
Accident
Injuries
No one was hurt; 1 person was on board or involved.
Weather
visual conditions (good weather)
Aircraft
Beech 23 · all 23s on the register
Registration
N1923L · no longer on the register · serial M-1826
Damage
Substantial damage
Flight
Personal flight · general aviation rules (Part 91)

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

The student pilot was conducting touch-and-go landings. During an approach to a landing, he initiated a go-around. As he applied full throttle, the airplane entered a "hard left bank," and the student pilot countered with right rudder. The airplane struck the ground in a left-wing-down attitude. There were no mechanical anomalies with the airplane, and the winds were aligned with the runway at 6-9 knots. The student pilot had accumulated a total of 42 hours of flight time. According to the Pilot's Handbook of Aeronautical Knowledge, "during takeoffs and climbs, when the effect of torque is most pronounced, the pilot must apply sufficient right rudder pressure to counteract the left-turning tendency and maintain a straight takeoff path."

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: student
  • Flight time: 44 hours in all; 13 in the last 90 days; 7 in the last 30 days; 13 as pilot in command
  • Medical certificate: Class 3 (valid medical--no waivers/lim.)
  • Seat: left
  • Injury: no injuries

The aircraft

  • Last inspection: annual inspection
  • Maximum gross weight: 2,460 lb
  • Seats: 4
  • Landing gear: fixed
  • Engine: Lycoming O-360 (piston); 0 hours total

The flight

  • Departed from: SEG PA
  • Flight plan: none
  • Runway 17, 3,800 ft by 75 ft

Weather at the time

  • Light: daylight
  • Wind: from 180° at 8 knots
  • Visibility: 10 statute miles
  • Sky: broken clouds at 6,000 ft; not recorded
  • Temperature: 73°F (23°C), dew point 55°F (13°C)
  • Altimeter: 29.00 inHg
  • Observation at 9:53 pm from SEG

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.

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