NYC92LA013 · I.C.A. Brasov LARK I-28-B2 LARK I-28
Aero Club Albatross I.C.A. Brasov LARK I-28-B2 LARK I-28 · Accident: loss of control in flight on approach
From 1N7 to 1N7
Event
- NTSB case
- NYC92LA013
- 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
- General aviation
- 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 LARK I-28-B2 LARK I-28
- Aircraft type
- I C A Brasov LARK I-28-B2
- 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
- N350BB
- Operator
- Aero Club Albatross
- Onboard fatalities
- Unknown
- Route
- From 1N7To 1N7
- 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
- Part 91: General Aviation
- 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
- Loss of control in flight
- 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
- Stall/mush
- 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
- Pilot in command › Aircraft handling, not maintained
- Pilot in command › Flight controls, improper use of
- Pilot in command › Planned approach, improper
- Pilot in command › Stall/mush, inadvertent
Approximate · Estimated position: the centre of Blairstown, NJ, the place the record names. Not the accident site.
NTSB narrative
THE GLIDER WAS RETURNING FOR A LANDING WHEN IT LANDED SHORT OF THE RUNWAY. A WITNESS SAID THE APPROACH WAS FLAT WITH THE GLIDER BEING 'STRETCHED'. HE SAID HE SAW A WING DROP AND THE GLIDER LANDED IN A RECYCLING DEPOT ACROSS THE STREET FROM THE APPROACH END OF THE RUNWAY. THE GLIDER ROLLED APPROXIMATELY 30 FEET AND STRUCK A CHAIN LINK FENCE. THE PILOT INDICATED NO FLIGHT TIME BUT LISTED 1200 FLIGHTS IN GLIDERS.
Probable cause
AN IMPROPERLY PLANNED APPROACH WHICH RESULTED IN AN INADVERTENT STALL WITH INSUFFICIENT ALTITUDE FOR RECOVERY. A FACTOR RELATED TO THE ACCIDENT WAS IMPROPER USE OF THE FLIGHT CONTROLS BY THE PILOT.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record NYC92LA013
- Event ID
- 20001212X18373
- Case number
- NYC92LA013
- 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: 1c00650ecf175aee59f6ea4630ab58cfd1a6ee750f5befa713f41dc93e485d13; retrieved 2026-09-23T03:35:55.887Z.