Beech 95-B55 (T42A) accident near Pacific Grove, California, July 27, 2025
On July 27, 2025 at about 5:37 am local time, a 1974 Beech 95-B55 (T42A), registered N8796R, was substantially damaged in an accident during approach near Pacific Grove, California (Monterey Rgnl airport). It was a personal flight under general aviation rules (Part 91). 3 people were killed. The weather was instrument conditions (cloud, fog or low visibility).
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 October 5, 2026. Docket and reports at the NTSB.
What the record shows
- Date
- July 27, 2025 · about 5:37 am local time
- Place
- Pacific Grove, California · Monterey Rgnl · map
- Type
- Accident
- Injuries
- 3 people were killed.
- Weather
- instrument conditions (cloud, fog or low visibility)
- Aircraft
- Beech 95-B55 (T42A), built 1974 · all 95-B55 (T42A)s on the register
- Registration
- N8796R · registry record · serial TC-1807
- Damage
- Substantial damage
- Flight
- Personal flight · general aviation rules (Part 91)
The NTSB's narrative preliminary · quoted from the NTSB record
On July 26, 2025, about 2237 Pacific daylight time, a Beech 95-B55, N8976R, was substantially damaged when it was involved in an accident near Pacific Grove, California. The pilot and two passengers were fatally injured. The airplane was operated as a Title 14 Code of Federal Regulations Part 91 personal flight. Review of recorded radio communications from the Northern California Terminal Radar Approach Control (NorCal Approach) revealed that the pilot requested flight following to Monterey Regional Airport (MRY), Monterey, California, after departure from San Carlos Airport (SQL), San Carlos, California. The controller provided a transponder code and advised the pilot to remain outside of the San Francisco Class Bravo airspace, to which the pilot acknowledged. The recordings depicted that the pilot had 3 frequency changes spanning the following 32 minutes. About 17 minutes after the pilot had obtained flight following, the controller obtained a Pilot Report (PIREP) from an airplane landing at MRY and quired the pilot if copied the PIREP, which the pilot acknowledged. The pilot then informed the controller he had obtained the current weather for MRY and requested the instrument landing system (ILS) 10R approach. Subsequently, the pilot was cleared to MRY via the ILS 10R approach. During the approach, the controller saw that the airplane had descended below the minimum vectoring altitude, and quired the pilot as to whether he was going around. The pilot replied “yes,” he was going around and requested vectors back to ZEBED; the ILS initial approach fix. The controller issued instructions for the pilot to turn to a westerly heading and climb to 3,000 ft, which the pilot acknowledged. Shortly after, the controller issued low altitude alerts for the accident airplane and despite multiple attempts, no further radio communication was heard from the pilot. Recorded ADS-B data provided by the Federal Aviation Administration showed that the airplane departed from SQL, runway 30 at 2211:03, and made a climbing left turn toward the south, before it leveled off at 5,500 ft mean sea level (msl). The data showed that at 2230:01, the airplane began a descent to an altitude of 2,400 ft msl. At 2233:42, the airplane made a left turn to an easterly heading and descended to an altitude of about 1,600 ft msl. At 2236:00 the airplane initiated a left descending turn. The data showed that the airplane continued in the descending left turn until ADS-B contact was lost over the Pacific Ocean at 2237:11, at an altitude of 200 ft msl, about 50 ft south of the accident site as seen in figure 1. Figure 1: ADS-B Flight Overlay with Accident Location. Witnesses near the accident reported hearing an airplane overflying their residence several times. One witness also reported hearing erratic engine noises and a low-flying airplane in a level left turn over their residence. The witness stated that the airplane turned to the north and entered a nose-down attitude until it descended out of their visual range followed by a loud impact sound. At 2254, recorded weather at MRY was wind from 280° at 6 knots, visibility of 10 statute miles, ceiling overcast at 900 ft, temperature of 59°F, dew point 55°F, altimeter 29.99 inches of mercury, remarks included: an automated station with a precipitation sensor (AO2), and a ceiling height that varied between 600 and 1000 ft. The wreckage was located about 300 ft from the shoreline, submerged in water, at a depth of about 10 to 15 ft. The airplane was recovered to a secure location for further examination.
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
- Loss of control in flight during approach defining event
The aircraft
- Airframe total time: 1,108.2 hours
- Last inspection: annual inspection, November 1, 2024
- Seats: 6
- Landing gear: retractable
- Operator: Sea2Sky Aviation LLC
The flight
- Departed from: SQL San Carlos CA at 5:11 am
- Destination: MRY Monterey CA
- Flight plan: IFR
Weather at the time
- Light: night
- Wind: from 280° at 6 knots
- Visibility: 10 statute miles
- Sky: overcast at 900 ft
- Temperature: 59°F (15°C), dew point 55°F (13°C)
- Altimeter: 30.03 inHg
- Observation at 10:54 pm from KMRY, 4 miles away
Weather report (METAR): KMRY 270554Z AUTO 28006KT 10SM OVC009 15/13 A3003 RMK AO2 CIG 006V010 SLP181 T01500133 10189 20150 50005
Injuries
| Fatal | Serious | Minor | None | |
|---|---|---|---|---|
| Flight crew | 1 | |||
| Passengers | 2 |
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.
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 never names anyone involved. A preliminary report can change; the final report usually follows one to two years later, and the page is refreshed when it does.
