FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

ERA14WA026 · Luscombe 8 - E

14 Oct 2013 · Buenos Aires, Argentina

Luscombe 8 - E · Accident: VFR encounter with IMC on approach

From SATE · Zarate to SMUS · Chascomus

Report a problem

Event

NTSB case
ERA14WA026
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
Unknown · led by another country; figures from NTSB notifications
API-reported fatalities
2 · all aircraft and ground
Ground fatalities
Unknown
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
Instrument Meteorological Cond

Luscombe 8 - E

Aircraft type
Luscombe 8
Category
Airplane
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
LV-RTS
Operator
Unknown
Onboard fatalities
Unknown
Route
From SATE · ZarateTo SMUS · Chascomus
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
Non-U.S., Non-Commercial
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
Defining eventThe 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
VFR encounter with IMC
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

No findings designated as a cause are recorded in the NTSB data yet.

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

NTSB narrative

On October 14, 2013, about 1134 coordinated universal time, a Luscombe 8E, Argentina registration LV-RTS, was substantially damaged, during descent in thick fog, when it impacted terrain in an industrial park. The flight had departed Zarate Airport (SATE), Buenos Aires Province, Argentina and was enroute to Chascomus Airport (SMUS), Buenos Aires Province, Argentina, when the accident occurred. The pilot and passenger were fatally injured.

This investigation is under the jurisdiction of the Government of Argentina.

Further information can be obtained from:

Junta de Investigaciones de Accidentes de Aviación Civil 1370 Belgrano Avenue 11th Floor Buenos Aires, República Argentina C1093AAO Fax - 54-11-4381-6333

This report is for informational purposes, and contains only information released by the Government of Argentina.

Verbatim NTSB factual narrative from the NTSB dataset

Sources

NTSB record ERA14WA026
Event ID
20131028X25130
Case number
ERA14WA026
Dataset
full-current
Source SHA-256
5cf380f0061817c0331a6b2d8cc7e0ee3a79bea469a1001dc5c10e56f35f5ab3
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.
  • No bulk values were replaced by the NTSB case API.
  • The date is the local date, which is the same as the UTC date the NTSB stores.
  • API snapshot SHA-256: 9f8206f27f49d712ba3f7f85902d6567727adf5eb9128e095340256b57d3d7df; retrieved 2026-09-14T16:06:08.738Z.