FLIGHT FINDINGSAVIATION OCCURRENCE MAP
Back to map

Cape Air Flight 415

30 Jan 2001 · Edgartown, MA, United States

Cessna 402C · Accident: in flight collision with object on approach

From Rhode Island T. F. Green International Airport (PVD) to Martha's Vineyard Airport (MVY)

Report a problem

Event

NTSB case
NYC01FA073
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
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

Cessna 402C

Aircraft type
Cessna 402
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
N6837Y
Operator
Cape Air
Onboard fatalities
Unknown
Route
From Rhode Island T. F. Green International Airport (PVD), Providence, RITo Martha's Vineyard Airport (MVY), Edgartown, MA
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
Approach · IFR final approach
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
In flight collision with object
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
Tree(s)
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

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

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

NTSB narrative

The pilot departed on a scheduled flight conducted under night instrument meteorological conditions. Arriving in the area of the destination airport, the weather was reported as, winds from 220 degrees at 18 knots, gusts to 25 knots; 1/2 statute miles of visibility and haze; vertical visibility of 100 feet. The pilot was vectored and cleared for the ILS 24 approach. As the airplane crossed the glideslope, the pilot observed that the "ride" became increasingly bumpy and turbulent, with a strong wind component from the right. The approach lights came into view as the airplane neared the runway, but soon disappeared due to the low visibility. The pilot executed a missed approach, and as full power was applied, the airplane began to move laterally to the left. During the missed approach, a "thunk" was heard on the left side of the fuselage, and the airplane descended into the trees. The airplane came to rest in a wooded area about 1/4 mile from the Runway 24 threshold, about 1,000 feet to the left of the extended centerline. Review of the approach plate for the ILS 24 approach revealed that the glide slope altitude at the final approach fix for the non-precision approach, which was located about 4 miles from the approach end of the runway, was 1,407 feet. The glide slope altitude at the middle marker, which was located about 0.6 miles from the approach end of the runway, was 299 feet. Review of radar data revealed that the airplane intercepted the glideslope about 4 miles from the threshold of runway 24. In the following 2 minutes, 30 seconds, the airplane deviated below and returned to the glideslope centerline approximately 4 times, with a maximum deviation of 2-dots below the glideslope centerline. About 1-mile from the runway, the airplane began a trend downward from the glideslope centerline, descending below the 2-dot low deviation line of the glideslope to an altitude of about 300 feet, when the last radar hit was recorded. During the approach, the airplane's groundspeed varied between 50 and 125 knots. According to the Aeronautical Information Manual chapter on Navigation Aids, Instrument Landing System (ILS), it stated that "Make every effort to remain on the indicated glide path." It also cautioned the pilot to, "Avoid flying below the glide path to assure obstacle/terrain clearance is maintained."

Probable cause

The pilot's failure to maintain a stabilized approach with an adequate vertical and lateral track. Also causal was his failure to maintain obstacle clearance.

Verbatim NTSB analysis and probable cause from the NTSB dataset

Sources

NTSB record NYC01FA073
Event ID
20010209X00426
Case number
NYC01FA073
Dataset
historical-pre2008
Source SHA-256
89e2df6d848e7ab3b42e7d7c7a03ff403303057a26ca04c95b3ea67201c3ce74
Source notes (5)
  • 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, coordinates. 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: bf72d0ec4193acb9aae14a691196fa9a1854d45e7ba8eba35a5cfcaf6d8b911a; retrieved 2026-09-18T16:17:09.786Z.
  • The NTSB's operator name is blank for N6837Y; the operator shown is the name the NTSB records it doing business as.