FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

SEA99TA051 · I.C.A. Brasov IS-28B2

14 Apr 1999 · North Plains, OR, United States

I.C.A. Brasov IS-28B2 · Accident: in flight collision with object on approach

Report a problem

Event

NTSB case
SEA99TA051
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
Completed
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
Government
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

I.C.A. Brasov IS-28B2

Aircraft type
I C A Brasov IS-28
Category
Glider
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
N843
Operator
Unknown
Onboard fatalities
Unknown
Route
From not recordedTo not recorded
Aircraft age
Not recorded
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
Public Aircraft
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
Approach · VFR pattern final
First occurrenceThe 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
In flight collision with object
Also codedOther events the NTSB coded in the sequence, such as a wire strike after a loss of power. Flight Findings uses them for its kinds of event. Glossary
Wire, transmission
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

  • Copilot/second pilot › Clearance, not maintained

Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.

NTSB narrative

The pilot-in-command reported that during the currency flight for the second pilot, the second pilot deployed the spoilers and the glider started to descend too soon while on final approach. The PIC stated that he shoved the spoilers closed and looked for the power lines that were near the approach end of the runway. The glider passed over the tops of trees, but did not clear the power lines. The glider collided with the upper power lines which slid up and over the canopy, breaking the Plexiglas over the aft seat. The second pilot was able to maintain pitch and roll in a level attitude as the glider dropped to the ground and landed hard on the main gear. Both pilots reported that they were aware of the power lines at this end of the runway. The PIC stated that he should have reminded the second pilot about the power lines, but didn't. The second pilot stated that he had never landed on this runway before and thought that the power lines were further from the end of the runway. He also thought that he might have been distracted by the tow plane which was landing on the parallel airstrip.

Probable cause

The second pilot did not maintain clearance from power lines. The pilot-in-command did not adequately supervise the second pilot, and the second pilot's diverted attention and lack of familiarity with the geographic area were factors.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record SEA99TA051
Event ID
20001205X00573
Case number
SEA99TA051
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
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. 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: f513c2fa31fc524d9228033ca084d3cfe5f48e837c6ec13ee79a910522c7baf7; retrieved 2026-09-18T21:21:16.424Z.