The U.S. aircraft register, updated daily
Accidents · NTSB ERA26LA246 · Preliminary: the investigation is not finished

Cessna 402 accident near Provincetown, Massachusetts, June 15, 2026

On June 15, 2026 at about 12:10 pm local time, a 1985 Cessna 402, registered N499CA, was substantially damaged in an accident during landing (flare/touchdown) near Provincetown, Massachusetts (Provincetown Municipal Airport). It was flown under charter and air-taxi rules (Part 135). 1 person was seriously injured; 2 others were unhurt. The weather was visual conditions (good weather).

The NTSB's probable cause their words, unchanged

The NTSB has not yet published a probable cause for this accident. Investigations usually take one to two years; this page updates when the final report is released.

Source: NTSB aviation accident database, copy made November 2, 2026. Docket and reports at the NTSB.

What the record shows

Date
June 15, 2026 · about 12:10 pm local time · cases in 2026
Place
Provincetown, Massachusetts · Provincetown Municipal Airport · cases near this airport · map
Type
Accident
Injuries
1 person was seriously injured; 2 others were unhurt.
Weather
visual conditions (good weather)
Aircraft
Cessna 402 C, built 1985 · all 402s on the register
Registration
N499CA · registry record · serial 402C1006
Damage
Substantial damage
Flight
Flight · charter and air-taxi rules (Part 135)

The NTSB's narrative preliminary · quoted from the NTSB record

On June 15, 2026, about 0810 eastern daylight time, a Cessna 402C, N499CA, was substantially damaged when it was involved in an accident at Provincetown Municipal Airport (PVC), Provincetown, Massachusetts. The airplane transport pilot (pilot flying) and commercial pilot (pilot monitoring) were not injured, while one passenger sustained serious injuries. The airplane was operated as a Title 14?Code of Federal Regulations Part 135, scheduled commuter flight. The pilot flying (PF) stated that the reported weather at the destination airport of PVC prior to departure was 5 statute miles visibility and an overcast ceiling of 200 ft, while the forecast weather of a nearby airport indicated a visibility of 3 statute miles and an overcast ceiling of 300 ft. The departure and en route portions of the flight to PVC were uneventful. After leveling at 3,000 ft msl, the flight crew obtained the current weather for PVC, which included a wind from 190° at 8 knots, a visibility of 5 statute miles, and an overcast ceiling at 200 ft agl. Because of the ceiling, the PF chose to execute an instrument landing system (ILS) approach to runway 07, which would have resulted in a tailwind component less than 3 knots, and was within the operator’s limitations. The flight was provided with radar vectored by air traffic control for the ILS runway 07 approach. The localizer and glideslope capture occurred at PHONY intersection while the airplane was flying at an altitude about 2,000 ft msl. At that time the airplane configured for landing with a flap setting of 15°. During the subsequent descent, the PF disconnected the autopilot and extended the flaps to 30° to further reduce airspeed, then extended the flaps to 45° once the airplane had reached about 600 ft. At decision height, he visually acquired the approach end of runway 07 and continued the landing approach. The PF stated that during the visual portion of the landing approach, the airplane was slightly above the desired glide path and was drifting to left of the runway centerline. The PF reduced engine power earlier than usual, resulting in a rapid increase in descent rate, and the last airspeed he recalled observing was 100 knots. The pilot monitoring (PM) reported that the PF seemed to, “over flare, causing us to float.” The airplane floated past the runway aiming point markings, then when approaching the mid-point of the 3,502-ft-long, wet runway, the PM called aloud for a go-around, but he was not sure if the PF heard him. The PF continued the landing, reporting the touchdown was farther along the runway than planned. After touchdown, the PF braked more aggressively than normal. As the airplane approached the departure end of the runway, the PF recognized that the airplane’s speed was still excessive, so he attempted to exit the runway via the taxiway off the left side of the runway at the end. The PM reported that he yelled “don’t” and within a second the PF corrected back. The airplane then departed the end of the runway, the right main landing gear collapsed, and the airplane came to rest upright in grass. After coming to a complete stop, the PF secured the airplane and initiated an emergency evacuation of the passenger. Airport and local emergency response personnel arrived shortly thereafter.

The complete narrative as the NTSB published it. The NTSB's docket holds the report as a PDF and any photographs, statements and other documents from the investigation.

The factual record from the NTSB's investigation tables, in plain English

What happened, in order

  1. Runway excursion during landing (landing roll)
  2. Landing gear collapse during landing (landing roll)
  3. Landing area overshoot during landing (flare/touchdown) defining event

The aircraft

  • Airframe total time: 28,835 hours
  • Last inspection: approved inspection programme, May 26, 2026
  • Maximum gross weight: 7,210 lb
  • Seats: 10
  • Landing gear: retractable
  • Operator: Hyannis Air Service INC

The flight

  • Departed from: BOS Boston MA at 11:40 am
  • Flight plan: IFR
  • Runway 07, 3,502 ft by 100 ft
  • A second pilot was aboard

Weather at the time

  • Light: daylight
  • Wind: from 190° at 8 knots
  • Visibility: 5 statute miles
  • Sky: overcast at 200 ft
  • Temperature: 68°F (20°C), dew point 32°F (0°C)
  • Altimeter: 29.58 inHg
  • Observation at 8:00 am from KPVC

Weather report (METAR): KPVC 151156Z AUTO 19008KT 5SM HZ OVC002 20/ A2958 RMK AO2 SLP015 6//// 7//// T0200 10206 20194 55006 PNO $

Injuries

FatalSeriousMinorNone
Flight crew2
Passengers1

Documents from the investigation the NTSB's docket: the evidence folder behind the report

The NTSB has not released the docket for this case yet. The docket, the folder of records gathered during an investigation (maintenance records, photographs, witness statements, examinations), is usually released when the investigation is nearly complete, and the list here is refreshed when it appears. Check at the NTSB.

Connections how this case links to the rest of the register

Aircraft
Place

The whole map of how records connect · these connections as data: /graph/accident/ERA26LA246.json.

The bigger picture in Aviation Analytics: accidents over time since 1982, by model, by phase of flight and conditions, by place and on the map.

Everything on this page comes from the NTSB's public records. The narrative, probable cause and findings are the NTSB's own words; the coded tables behind the report are written out in plain English, with pilots' ages, home towns and medical details left out. The documents and photographs are the NTSB's docket, shown as the NTSB released them. This site's own text does not name anyone involved, its policy at this time. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.