ERA18LA112 · Gulfstream Aerospace G V UNDESIGNAT
Peyton Holdings Gulfstream Aerospace G V UNDESIGNAT · Accident: turbulence encounter en route
From Rio de Janeiro Galeão – Tom Jobim International Airport (SBGL) to Miami, FL
Event
- NTSB case
- ERA18LA112
- 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
- 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
Gulfstream Aerospace G V UNDESIGNAT
- Aircraft type
- Gulfstream G
- 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
- N90JE
- Operator
- Peyton Holdings
- Onboard fatalities
- Unknown
- Route
- From Rio de Janeiro Galeão – Tom Jobim International Airport (SBGL), Rio de JaneiroTo Miami, FL
- Aircraft age
- About 20 years (built 1998)
- 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
- En route · descent
- 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
- Turbulence encounter
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- None
Cause areas
- Environmental issues › Conditions/weather/phenomena
- Personnel issues › Action/decision
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
During their descent for arrival, the flight crew of the business jet illuminated the fasten seatbelt sign. They cycled the seatbelt sign again when the airplane began encountering light turbulence. After deviating left of some adverse weather that was displayed on radar, they continued their descent and encountered moderate turbulence and heavy rain, during which the airplane dropped about 500 to 1,000 ft. Despite the flight crew having warned the passengers by cycling the seatbelt sign during their descent from cruise altitude, three of the five passengers were not wearing seatbelts during the turbulence encounter. One of the unbelted passengers was seriously injured, while the other two incurred minor injuries. The flight subsequently landed without further incident.
Probable cause
The passengers' failure to comply with the fasten seatbelt sign, with resulted in their injury during an inflight turbulence encounter.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA18LA112
- Event ID
- 20180322X42204
- Case number
- ERA18LA112
- 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.
- Filled from the NTSB case API where the bulk record had no value: investigation status, damage. 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: b6f02d06b6c1072ea2a1d1b61803455d713e704dfac999aa63d690e4adba1b5a; retrieved 2026-09-16T06:41:44.338Z.