# Accident 19980401005279A: Beech 35C33, Portland, OR, April 1, 1998

- Type: FAA accident report (Accident/Incident Data System), as reported
- Date: April 1, 1998, 11:10 local time
- Place: Portland, OR
- Airport: Portland/Hillsboro Airport
- Damage: Substantial damage
- Phase of flight: To Init Climb(1st Pwr Reduct)
- Operating rules: General operating rules (Part 91)
- Location: 45.4392° N, 122.9608° W: From the FAA, an estimate near the named town, within about 3 miles
- Nearby events: https://openairdocs.org/map.md?lat=45.4392&lon=-122.9608&mi=10
- Aircraft: N1310A, registered now (https://openairdocs.org/aircraft/N1310A) (OpenAirDocs)
- Registry model: Beech 35-C33 (registry code 1151408, https://openairdocs.org/model/beech-35-c33) (OpenAirDocs)
- Registry engine: Continental I0-470 series (registry code 17027, https://openairdocs.org/engine/continental-i0-470-series) (OpenAirDocs)
- Reported make and model: BEECH 35C33
- Reported engine: CONT IO470K
- People aboard: 2
- Fatal injuries: 0
- Pilot flight hours: 1,050 total, 320 in this make and model, 21 in the last 90 days
- NTSB investigation: [NTSB SEA98LA059](https://openairdocs.org/ntsb/SEA98LA059) (OpenAirDocs)
- FAA source: FAA Aviation Safety Information Portal (https://asip.faa.gov/)
- Page: https://openairdocs.org/incident/19980401005279A

## Narrative

As the FAA filed it, in capitals; the FAA replaces private details with ^PRIVACY DATA OMITTED^.

STUDENT MADE PREMATURE LIFTOFF. SETTLED. WING DIPPED CFI CONTINUED WITH DUAL. ON LANDING FOUND WING DAMAGED. (.4)WHILE PRACTICING SOFT-FIELD TAKEOFFS IN A SINGLE-CONTROL THROW-OVER YOKE AIRCRAFT, THE STUDENT PULLED THE AIRCRAFT OFF THE RUNWAY PRIOR TO ATTAINING ENOUGH SPEED TO REMAIN AIRBORNE. IMMEDIATELY AFTER BECOMING AIRBORNE, THE AIRCRAFT BANKED SHARPLY TO THE LEFT, DROPPED ONTO THE RUNWAY, AND BOUNCED BACK INTO THE AIR. ACCORDING TO THE INSTRUCTOR PILOT, WHEN HE SAW THAT THE AIRCRAFT WAS GOING TO LIFT OFF PREMATURELY, HE COMMANDED THE STUDENT TO LOWER THE NOSE. BUT, THE STUDENT DID NOT LOWER THE NOSE ENOUGH, AND THE INSTRUCTOR DID NOT APPLY FORWARD PRESSURE TO THE CENTRAL CONTROL PEDESTAL TO KEEP THE AIRCRAFT FROM LIFTING OFF TOO EARLY. IT WAS LATER DISCOVERED THAT THE LEFT WING HAD IMPACTED THE ASPHALT SURFACE WHEN THE AIRCRAFT DROPPED BACK ONTO THE RUNWAY.                                                           (-23)FLIGHT INSTRUCTOR,^PRIVACY D^, WITH STUDENT, LIFTED OFF PREMATURELY AND AIRCRAFT CAME DOWN HARD.  THEY CONTINUED TO TAKEOFF, LANDED AND INSPECTED AIRCRAFT.  FLEW AIRCRAFT MORE WITH STUDENT.  WHEN AIRCRAFT WAS PUT AWAY IN                                         THE HANGER FOR THE DAY. ^PRIVACY D^ NOTICED TEH DAMAGE TO BOTTOM OF LEFT WING SHOWED CONTACT.  AFT TRAILING EDGE TIP WAS BUCKLED AND AILERON BUCKLED OUTBOARD HINGE.

## The NTSB's investigation of this event (1)

From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model.

- [NTSB SEA98LA059](https://openairdocs.org/ntsb/SEA98LA059), Apr 1, 1998: Beech 35-C33 (N1310A), Hillsboro, OR, substantial damage. Probable cause: The flight instructor's inadequate supervision and the dual student's premature lift off which resulted in inadequate airspeed, a stall, and collision with the ground.

## Other reports on N1310A (2)

Matched to the same aircraft by N-number and date.

- [Accident 20250906019509A](https://openairdocs.org/incident/20250906019509A), Sep 6, 2025: Beech 35-C33 (N1310A), Brookings, SD, Destroyed. The flight was to view a football game in bozeman, MT. The intended flight plan Was a VFR flight from kbkx to krap for fuel, then from krap to kbzn via an IFR…
- [Accident 19990417018649A](https://openairdocs.org/incident/19990417018649A), Apr 17, 1999: Beech 35C33 (N1310A), Portland, OR, Substantial damage. (.19) On April 17, 1999, approximately 1700 pacific daylight time, a Beech C33, N1310A, experienced a landing gear inadvertent retraction or collapse on the…

From the FAA Accident/Incident Data System. Reports are matched to registry aircraft by N-number and event date, checked against the reported make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. For accidents, the NTSB's own investigation is the fuller record.

---
OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.