Webstas Aviation Services Rockwell International 690B accident
Rockwell International 690B · Accident: controlled flight into terrain/object (CFIT) en route
From Terrance B. Lettsome International Airport (TUPJ) to TSJU · San Juan, PR
Event
- NTSB case
- ERA09FA078
- 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
- 3 · 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
- Charter & commuter
- 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
Rockwell International 690B
- Aircraft type
- Rockwell 690
- 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
- N318WA
- Operator
- Webstas Aviation Services
- Onboard fatalities
- Unknown
- Route
- From Terrance B. Lettsome International Airport (TUPJ), TortolaTo TSJU · San Juan, PR
- 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 135: Air Taxi & Commuter
- 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
- Controlled flight into terrain/object (CFIT)
- DamageDestroyed: beyond practical repair. Substantial: damage that affects the structure, performance or handling and normally needs major repair. Minor: less than that. Glossary
- Destroyed
Cause areas
- Personnel issues › Action/decision
- Personnel issues › Task performance
Approximate · Coordinates as recorded by the NTSB; no uncertainty radius is established.
NTSB narrative
The charter flight departed for the destination, where the passengers would connect with another airline flight. The instrument-rated pilot may have felt pressured as the flight departed late. The accident airplane approached the destination airport from the east, descending at 250 knots ground speed from 8,800 feet above mean sea level (msl), on a 270 degree assigned heading, and was instructed to enter the right downwind for runway 10. The airplane's altitude readout was then observed by the approach controller to change to "XXX." The pilot was queried regarding his altitude and he advised that he was descending to 3,200 feet msl. The pilot was asked to confirm that he was in visual flight rules (VFR) conditions and was advised that the minimum vectoring altitude (MVA) for the area was 5,500 feet msl. The pilot responded that “We just ahh,” at which time the controller advised that she missed his transmission and asked him to repeat it. The pilot stated “Ahh roger, could we stay right just a little, we are in and out of some clouds right now.” The controller advised the pilot to “Maintain VFR” and again of the MVA. The controller then made multiple attempts to contact the pilot without result. The wreckage was discovered on the side of a mountain, where the airplane impacted after entering instrument meteorological conditions. Because aircraft operating in VFR flight are not required to comply with minimum instrument altitudes, aircraft receiving VFR radar services are not automatically afforded Minimum Safe Altitude Warning services except by pilot request. The controller's query to the pilot about his altitude and flight conditions was based on her observation of the loss of altitude reporting information. The pilot had not indicated any difficulty in maintaining VFR flight or terrain clearance up to that point. His comment that the aircraft was "in and out of some clouds" was her first indication that the pilot was not operating in visual conditions, and came within seconds of impact with the terrain. The controller was engaged in trying to correct the situation, and despite having been advised of the minimum vectoring altitude, the pilot continued to descend. The airplane was equipped with a terrain avoidance warning system but it could not be determined if it was functional. The pilot owned the charter operation. Documents discovered in the wreckage identified the pilot and airplane as operating for a different company since the pilot did not have the permissions necessary to operate in the United Kingdom Overseas Territories.
Probable cause
The pilot's continued visual flight into instrument meteorological conditions, which resulted in an in-flight collision with terrain.
Verbatim NTSB analysis and probable cause from the NTSB dataset
Sources
NTSB record ERA09FA078
- Event ID
- 20081203X44941
- Case number
- ERA09FA078
- 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. 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: 91e9ed34f64cd6a9f0f070d4eca8ed4342ec1de12f2600f7e82794b4a80c4bd5; retrieved 2026-09-13T19:51:03.434Z.