FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

NYC04FA223 · Aero Commander 112

15 Feb 2004 · Vieques, PR, United States

Aero Commander 112 · Accident: airframe, component or system failure en route

From Luis Munoz Marin International Airport (TJSJ) to Henry E. Rohlsen Airport (TISX)

Report a problem

Event

NTSB case
NYC04FA223
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
1 · 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
Visual Meteorological Cond

Aero Commander 112

Aircraft type
Aero Commander 112
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
N1261J
Operator
Unknown
Onboard fatalities
Unknown
Route
From Luis Munoz Marin International Airport (TJSJ), San Juan, PRTo Henry E. Rohlsen Airport (TISX), Christiansted
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
En route · cruise
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
Airframe, component or system failure
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
Visual flight rules (VFR) flight into instrument meteorological conditions (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

  • Pilot in command › In-flight planning/decision, inadequate
  • Pilot in command › Preflight planning/preparation, inadequate

Approximate · Coordinates from the NTSB case API, which marks them as estimated or does not say; no uncertainty radius is established.

NTSB narrative

While proceeding eastbound at night along the shoreline of an island, the airplane began a rapid spiral descent, and impacted the ground. Despite an extensive search by multiple entities, the airplane remained missing for approximately 4 years; however, when the wreckage was located, there was sufficient evidence to show that the vacuum pump, which powered the attitude indicator and the directional gyro, had failed. Examination of Federal Aviation Administration (FAA) records revealed that the airplane had accrued in excess of 1,224.8 total hours of operation, but no evidence of the vacuum pump ever being overhauled or replaced was discovered. The pilot did not possess an instrument rating, and most likely had not flown at night for approximately 10 years. The airplane was equipped with an autopilot; however, the pilot was reported not to be experienced in its use. Taking into consideration the direction of flight, available weather data, and the lack of ground lights in the area, there would have been no visible horizon forcing the pilot to maintain control of the airplane solely by referencing the flight instruments. It has been well documented that such conditions can result in a myriad of vestibular illusions which can be extremely difficult to overcome. One illusion in particular can cause a pilot to believe the airplane is in level flight, when in reality, it is in a gradual turn. If the airspeed increases, the pilot may experience a postural sensation of a level dive and pull back on the yoke, which tightens the turn. If recovery is not initiated, a steep spiral will develop and continue until the airplane impacts the ground or water. The FAA's Airplane Flying Handbook states that "unless a pilot has many hours of training in instrument flight, flight in reduced visibility or at night when the horizon is not visible should be avoided." FAA Advisory Circular AC 91-75, highlights that pilots tend to rely heavily on the attitude indicator in instrument meteorological conditions, and that vacuum system failures can be a significant cause or contributor to fatal accidents because in most cases the corresponding instruments slowly becomes inaccurate, making the failure difficult to recognize.

Probable cause

The pilot's inadequate preflight and in-flight planning and decision making which resulted in the airplane entering instrument meteorological conditions. Contributing to the accident was the pilot's lack of instrument experience, a vacuum pump failure, and the night lighting conditions.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC04FA223
Event ID
20080425X00545
Case number
NYC04FA223
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: local date, investigation status, coordinates. Values present in the bulk record are kept.
  • The date is the local date; the NTSB stores the UTC date 2004-02-16.
  • API snapshot SHA-256: e73d5de82f01d8719adf7b944e466f0596f5d2e344118e66d724b5e1a4633900; retrieved 2026-09-20T18:33:58.592Z.