Plane crash map Locate crash sites, wreckage and more

N4615D accident description

Massachusetts map... Massachusetts list
Crash location 42.024723°N, 71.142777°W
Nearest city South Easton, MA
42.047322°N, 71.081436°W
3.5 miles away
Tail number N4615D
Accident date 12 Aug 2008
Aircraft type Beech G35
Additional details: None

NTSB Factual Report


On August 12, 2008, about 1017 eastern daylight time, a Beech G35, N4615D, registered to a private individual, operated by the pilot as "Angel Flight 15 Delta" experienced an in-flight loss of control while maneuvering to re-intercept a final approach course, and then crashed into a parking lot of a shopping center located in South Easton, Massachusetts. Instrument meteorological conditions prevailed at the time and an instrument flight rules (IFR) flight plan was filed for the 14 Code of Federal Regulations (CFR) Part 91 personal flight that departed Francis S. Gabreski Airport (FOK), Westhampton, New York, about 0909, destined for General Edward Lawrence Logan International Airport (BOS), Boston, Massachusetts. The airplane was destroyed, and the certificated commercial pilot and the two passengers were killed.

The pilot was flying the passengers to BOS so one of the passengers could receive medical treatment in the Boston area.

After takeoff the pilot established contact with New York Terminal Radar Approach Control, and then with Providence Air Traffic Control Tower, while proceeding towards the destination airport. Air traffic control (ATC) communications were then transferred to Boston Consolidated Terminal Radar Approach Control (Boston Consolidated TRACON).

According to a transcription of communications with Boston Consolidated TRACON Initial Departure Position, the pilot contacted the facility at 0954:05, and advised the controller that he had automated terminal information service (ATIS) information Papa. The controller instructed the pilot to expect the instrument landing system (ILS) approach to runway 4R, and provided the altimeter setting. The flight continued towards the destination airport and the controller instructed the pilot to turn 10 degrees left from his current heading of 030 degrees. The pilot responded that he was turning to heading 040 degrees, but the controller did not correct the incorrect readback. The flight was given several more heading changes, and the controller informed the pilot to expect to be turned onto the downwind leg. At 1008:08, the controller vectored the pilot to fly heading 220 degrees, which the pilot acknowledged.

Air traffic control communications were transferred to the Boston Consolidated TRACON Final 1 position and on the pilot’s first contact at 1008:30, he informed the controller he was turning to heading 210 degrees, though approximately 22 seconds earlier he was previously instructed to fly heading 220 degrees. Approximately 1 minute 49 seconds later the controller instructed the pilot to turn 10 degrees to the right and descend and maintain 4,000 feet. The pilot acknowledged the heading and altitude clearances and radar data depicted the airplane flying the heading and descending with a ground speed of approximately 170 knots. At 1013:01, when the flight was approximately 21 nautical miles southwest of BOS flying at 4,200 feet msl, the controller instructed the pilot to turn to heading 170 degrees. The pilot acknowledged and radar data depicted the heading change.

The transcription of communications further indicates that at 1013:42, the controller instructed the pilot to turn to heading 130 degrees and then instructed him to descend and maintain 3,000 feet msl; the pilot acknowledged both clearances and recorded radar data reflects the airplane flying in a southeasterly heading. At 1014:44, when the flight was about 3,500 feet msl and approximately 1.5 statute miles west of the ILS 4R localizer at 170 knots ground speed, the controller instructed the pilot to turn left heading 060 degrees and to intercept the localizer. The pilot acknowledged the instructions and recorded radar data indicates a large radius turn to the left but the pilot flew thru the localizer flying in a east-northeasterly direction. At 1015:46, while flying at 3,300 feet msl on a heading of approximately 072 degrees approximately 1.6 statute miles east of the ILS 4R localizer, the controller instructed the pilot, “…you’re passing through the localizer turn left heading zero one zero intercept localizer.” The pilot responded with "one five Delta." After the pilot's truncated transmission, radar data indicated the flight turned left to a heading of approximately 320 degrees and descended to 2,800 feet msl then climbed to 2,900 feet msl. The recorded radar data depicted that between 1016:27, and 1016:39, the flight descended to 2,800 feet msl and turned to the right flying in a northerly direction. At 1016:39, the controller asked the pilot if he was joining the localizer; there was no response. At 1016:46, the controller instructed the pilot that the altitude indicated 2,300 feet, then immediately informed him radar contact was lost and ended the transmission with the partial call sign of the flight. The pilot responded with, "one five Delta with you."

The recorded radar data indicates that between 1016:39, and 1016:54, the airplane turned to the right heading in a southeasterly direction and descended to 1,900 feet msl. At 1016:57, the controller instructed the pilot that the flight was at 1,200 feet, issued a low altitude alert, and instructed the pilot twice to "climb immediately." The pilot responded "one five Delta’s climbing", and the recorded radar data indicates the flight turned to the left flying in a northwesterly direction and climbed to 2,200 feet msl. The controller advised the pilot to maintain 3,000 feet; and to state his heading. While the transcription of communications indicates the transmission from the pilot was unintelligible, review of the voice communication tape by the National Transportation Safety Board (NTSB) revealed the pilot responded, “15 Delta’s ah 020.”

The recorded radar data indicated that at 1017:27, the flight was at 2,700 feet msl and approximately 4 seconds later at 1017:31, the airplane was at 2,100 feet msl. The controller again instructed the pilot to maintain 3,000 feet and to state heading; there was no response. The controller then instructed the pilot that, "… your altitude is going up and down are you all right sir." There was no response. The controller then issued a low altitude alert again, instructed the pilot to climb immediately, and that radar contact was lost. The controller asked nearby aircraft if they heard a signal from an emergency locator transmitter; no signal was heard.

A witness who was on Route 106 reported to law enforcement seeing the airplane climbing and descending from the clouds.

A pilot-rated witness who was located .41 nautical mile north-northwest from the crash site reported hearing a low flying airplane, heading west to east, with high rpm. He ran outside but did not see the airplane. The noise faded then returned, and he observed the airplane descending vertically out of the clouds. The witness's first view of the airplane was the top of the airplane. He did not recall if he saw the landing gear, but did not see any smoke trailing the airplane during the time he saw it. The airplane spun 2.5 times to the left, went out of sight behind trees, and he heard an impact and saw smoke. He drove to the scene arriving there about 1 minute later. The witness added that the engine was running with a constant sound prior to impact, and that there was no missing or sputtering. The weather conditions at the time consisted of a ceiling at 800 feet, with no rain or wind.

One witness located adjacent to the accident site reported hearing the airplane then seeing it flying in a southerly direction at the base of or partially in the clouds. The airplane climbed into the clouds then heard it flying eastbound. About 15 to 20 seconds later he heard “coughing sounds,” followed by seeing the airplane emerge from the base of the clouds with no engine no operating. He then reported the engine began operating but was sputtering while the airplane was descending with the nose at an angle of about 45 degrees. He noted the airplane was turning clockwise at full throttle then abruptly began rotating counterclockwise. The witness did not see the impact but reported the engine was operating at high rpm before hearing the impact. He called 911 to report the accident, and reported that the cloud bases were low like hanging fog but there was no rain.

A witness who was located on the roof of a nearby store reported to law enforcement seeing the airplane flying low between their location and another nearby building. Numerous witnesses also reported to local law enforcement seeing the airplane circling and then nose diving into the parking lot.

The airplane impacted onto a parking lot during daylight conditions; the crash site was located approximately 212 degrees and 21 nautical miles from the center of BOS. There were no ground injuries or damage to any vehicles or equipment located in the parking lot.


The pilot, age 65, held a commercial pilot certificate with ratings airplane single engine land, airplane multi-engine land, and instrument airplane, issued September 4, 2003, and a second class medical certificate issued October 30, 2007, with a restriction to wear corrective lenses for near and distant vision.

Review of the pilot’s FAA certified medical file and also personal medical records obtained with consent from the pilot’s family was performed by the NTSB's Medical Officer. The review of the medical file and personal medical records revealed an FAA form 8500-14 (Ophthalmological Evaluation for Glaucoma) dated August 7, 2007, noted that the pilot had glaucoma treated with laser surgery and 3 different eyedrops, “trace” cataracts, and visual field deficits. Visual acuity on that date was noted (with correction) as 20/20 in the right eye and 20/20+2 in the left eye. The pilot’s Application for (2nd class) Airman Medical Certificate dated October 30, 2007, noted the glaucoma and treatment, and the issuance of a 2nd class medical certificate, without any further indication of additional evaluation. Ophthalmologist records were reviewed; they noted on February 15, 2008, that the pilot indicated his distant visual acuity was “not as clear as it used to be” and on May 13, 2008, the pilot’s visual acuity was noted to be “stable both eyes,” measured (with correction) at 20/20-2 and 20/25-2. Visual field examinations dated through February 15, 2008, documented persistent visual field deficits primarily in the upper half of the pilot’s visual fields in both eyes. The pilot’s personal medical records also documented an incident of several weeks of left sided facial numbness through December 18, 2008, though the pilot’s family reported no recollection of him complaining of any facial numbness.

NTSB review of the pilot’s 5th pilot logbook that begins with a “From” date of “1/1/2004” to the last entry dated July 28, 2008 (15 days before the accident), revealed a carry forward time of 1,408 hours. His family reported that he did not fly between the last logged flight and the accident date. Between the “From” date and the last entry in the 5th logbook, he logged approximately 113 hours total time, 12.8 hours as flight in actual instrument conditions, and executed 16 instrument approach procedures as pilot-in-command (PIC), all of which were in the accident airplane. His last flight review in accordance with 14 CFR Part 61.56 occurred on August 21, 2006. There was only 1 logged flight in which the pilot obtained simulated instrument instruction. The instruction occurred during the pilot’s flight review on August 7, 2004, which included three instrument approaches and .8 hour simulated instrument flight.

Further review of his No. 5 logbook for the previous 24 calendar months (August 1, 2006 to the accident date) revealed he logged 5.3 hours actual instrument flight time and seven instrument approaches as PIC. The dates of the instrument flights in the previous 24 calendar months that concluded with instrument approach procedures performed as PIC were August 4, 2006, February 3, 2008, and June 23, 2008. No logged actual or simulated instrument flight occurred between August 4, 2006, and February 3, 2008. Five instrument landing system (ILS) approaches were performed as PIC on June 23, 2008. A review of logbook entries in 12 calendar month intervals beginning with May 2004 (May 1, 2004 thru May 31, 2005), June 2005 (June 1, 2005 thru June 30, 2006), July 2006 (July 1, 2006 thru July 31, 2007), and August 2007 (August 1, 2007 thru the accident date), revealed he logged executing as PIC 4, 5, 1, and 6 instrument approach procedures respectively. There was no record that an instrument proficiency check was performed in the No. 5 logbook.


The airplane was manufactured in September 1956, by Beech Aircraft Corporation, as model G35, and was designated serial number D4807. It was powered by a Teledyne Continental Motors E-225-8 engine, and equipped with a Beech 215-107 constant speed propeller. It was also equipped with a single axis (roll) autopilot control system, and yaw damper.

Review of the maintenance records revealed the airplane was last inspected in accordance with (IAW) an annual inspection on August 9, 2007; the airplane total time at the time of the inspection was 3,739.94 hours. Based on the pilot’s logbook, he had operated the airplane for 30.3 hours since the last annual inspection. The pitot static system, altimeter, pressure altitude reporting system and transponder checks were last performed IAW 14 CFR Part 91.411 and 14 CFR Part 91.413 on October 23, 2006.

While the pilot documented airplane discrepancies in the remarks section of his 5th pilot logbook, a review of it revealed no entry documenting a discrepancy or malfunction with the primary or secondary flight controls, autopilot, yaw damper, flight instruments, or vacuum system.


A surface weather observation taken at BOS at 1015, or approximately 2 minutes before the accident, indicated the wind was from 350 degrees at 8 knots with gusts to 14 knots, the visibility was 8 statute miles with light rain, broken clouds existed at 1,100 and 2,000 feet, overcast clouds existed at 5,500 feet, the temperature and dew point were 17 and 15 degrees Celsius respectively, and the altimeter setting was 29.70 inches of mercury.


According to FAA personnel, there were no abnormalities with either the 4R Localizer or Glide Slope facilities on the accident date. The full ILS was operational that day. The Localizer and Glide Slope had a Periodic with monitors flight inspection on March 9, 2008. There was also a special flight inspection of the Localizer on April 28, 2008, for the purpose of an Expanded Service Volume authorization. Additionally, there were no unscheduled outages or abnormalities for the Glide Slope in the prior 12 month period; only scheduled maintenance was performed.

The Localizer had two reported incidents, none of which was associated with equipment performance abnormality. The first incident was associated with a snow outage; which was resolved by snow removal from the Localizer antenna's on January 14, 2008. The second incident was associated with a telephone line outage for the interlock signal. This incident was resolved on October 12, 2007, by restoration of a T-1 line from the Boston Air Traffic Control Tower (Boston ATCT) to the Boston Localizer (in Winthrop, MA) restoring the interlock signal to the facility.


The pilot was in contact with Boston Consolidated TRACON at the time of the accident; there were no reported communication difficulties.


BOS is equipped in part with runway 4R, which has an ILS or localizer approach. The approach requires radar or distance measuring equipment (DME).


Examination of the accident site revealed the airplane came to rest upright on a magnetic heading of 254 degrees. A ground scar associated with the right wing was noted just forward of the resting point of the right wing, the ground scar was oriented on a magnetic heading of 206 degrees. An impact crater associated with the engine was noted in the area where the airplane came to rest, and a propeller blade counterweight was

NTSB Probable Cause

The pilot's failure to maintain control of the airplane while attempting to execute an instrument approach in instrument meteorological conditions. Contributing to the accident was the pilot's lack of instrument currency.

© 2009-2020 Lee C. Baker / Crosswind Software, LLC. For informational purposes only.