N942SP

Destroyed
Fatal

Cessna 172SS/N: 172S8137

Accident Details

Date
Tuesday, June 4, 2002
NTSB Number
MIA02FA104
Location
Lutz, FL
Event ID
20020611X00849
Coordinates
28.127222, -82.525276
Aircraft Damage
Destroyed
Highest Injury
Fatal
Fatalities
1
Serious Injuries
0
Minor Injuries
0
Uninjured
0
Total Aboard
1

Probable Cause and Findings

The suicidal act by the pilot resulting in the in-flight collision with trees then the ground. A contributing factor in the accident was the pilot's depression. Findings in the investigation were the pilot's overdose of zolpidem and citalopram before the accident flight departed, and his intentional operation of the airplane while impaired by alcohol.

Aircraft Information

Registration
N942SP
Make
CESSNA
Serial Number
172S8137
Engine Type
Reciprocating
Year Built
1999
Model / ICAO
172SC172
Aircraft Type
Fixed Wing Single Engine
No. of Engines
1

Registered Owner (Historical)

Name
HELICOPTERS & AIRPLANES INC
Address
1013 CENTRE RD
Status
Deregistered
City
WILMINGTON
State / Zip Code
DE 19805-1265
Country
United States

Analysis

HISTORY OF FLIGHT

On June 4, 2002, about 0823 eastern daylight time, a Cessna 172S, N942SP, registered to Helicopters & Airplanes, Inc., collided with trees then the ground near Lutz, Florida. Visual meteorological conditions prevailed at the time and no flight plan was filed for the 14 CFR Part 91 personal, local flight. The airplane was destroyed by impact and the private-rated pilot, the sole occupant, was fatally injured. The flight originated about 0709 from Vandenberg Airport, Tampa, Florida.

The pilot was observed taxiing the airplane to runway 36 at the Vandenberg Airport, and one witness located on the airport reported the pilot did not perform an engine run-up before takeoff but he "gunned the throttle two times and took off at 0710 am." Another witness on the airport reported hearing the pilot run up the engine abruptly several times before observing the pilot taxi onto runway 36. An individual who was working at a fixed-base operator (FBO) at the Vandenberg airport reported that on the day of the accident sometime after 0730 hours, Tampa Approach Control contacted the FBO and asked for someone there to attempt to contact the pilot on the airport's common traffic advisory frequency (CTAF). She reported making repeated broadcasts on the CTAF for the accident pilot, but he did not respond.

According to a chronological sequence of events prepared by the air traffic manager of the Tampa International Airport Air Traffic Control Tower, at approximately 0716, a radar target associated with the accident airplane was noted orbiting at 2,000 feet north-northeast of the Tampa International Airport (KTPA). At approximately 0718, the departure controller questioned the tower controller about the orbiting airplane; the tower controller advised he was not aware of the airplane and it must be a class B airspace violator. At approximately 0726, the pilot of Flight Express 820 which was inbound to KTPA was vectored by a controller in the area of the orbiting airplane to help identify the airplane; he provided the registration of the airplane to the controller at approximately 0730. At approximately 0734, the Flight Express 820 pilot advised the controller that he thought the airplane was based at the Vandenberg Airport. At 0738, the operations supervisor contacted the FBO at Vandenberg who provided the name of the owner of the airplane. The FBO was also asked to attempt to communicate with the pilot on the airport UNICOM frequency. At 0742, the operations supervisor advised the tower controller that a police helicopter would become airborne to track the orbiting airplane. At approximately 0753, the operations supervisor contacted the U.S. Coast Guard requesting their assistance. At approximately 0758, the operations supervisor contacted the St. Petersburg Automated Flight Service Station and requested personnel attempt to communicate with the pilot of the orbiting airplane on the appropriate PIE VORTAC frequency. At approximately 0803, a flightcrew member of a police department helicopter reported on the frequency and the flight was vectored to the area of the orbiting airplane. A flightcrew member of the police department helicopter broadcast on 121.5 for the orbiting airplane, but there was no response from the pilot. At approximately 0812, a flightcrew member of the police department helicopter advised they would return to get a Cessna which had a camera. At approximately 0821:24, the radar target was lost momentarily, a target was reacquired at 0821:35, and the radar target was finally lost at 0823:10, with the last recorded altitude of 700 feet mean sea level.

The pilot of Flight Express 820 later reported in writing to the National Transportation Safety Board (NTSB) that while flying in close proximity to the accident airplane, he observed the pilot of the orbiting airplane sitting upright in the "left side of the aircraft." He also reported he thought the pilot of the orbiting airplane was aware of the close proximity of both airplanes because, "...it appeared that he was maneuvering to avoid me, although I was unable to see the pilot moving at any time nor was I close enough to see any facial expressions or physical gestures of any kind."

The pilot of the Tampa Police Department helicopter which was dispatched to the orbiting airplane reported observing the airplane from 3/4 mile away. He later reported the airplane was flying left orbits.

A witness near the accident site reported hearing the airplane flying at what she thought was a low altitude then heard the engine "revving" up followed by hearing the impact. Several other witnesses across the street from the crash site reported hearing the engine sound that was steady with no sputtering. The engine sound remained the same from the time they heard it until the impact. Another witness reported that he first observed the airplane when it was approximately 30-40 feet above the tops of trees. The airplane at that time was in a 80-degree nose low attitude on a southeast heading. He observed the airplane collide with the trees then heard the impact.

Several law enforcement aircraft and a U.S. Coast Guard helicopter were dispatched to the area of the last known position of the orbiting airplane. Additionally, a ground search for the airplane was initiated by local law enforcement personnel.

National Transportation Safety Board (NTSB) review of recorded radar data for beacon code 1200 radar returns revealed a target was first observed at 0709:07, at 400 feet mean sea level (msl) just north of runway 36 at the Vandenberg Airport. The flight proceeded in a northwest then westerly direction where from approximately 0715 to 0817, the flight orbited at approximately 2,200 feet over the intersection of Ehrlich Road and Dale Mabry Highway. At approximately 0817, the flight departed from the orbiting area and proceeded in a northwesterly direction for approximately 1.6 minutes, then turned to the right completing a 180-degree turn. The airplane then proceeded in a southeasterly direction for approximately 36 seconds and at approximately 0819:55, the airplane turned to the left and proceeded in a northerly direction flying at 2,100 feet until 0820:31. The airplane then turned to the left, climbed 100 feet over the next 12 seconds, then the airplane turned to the right and performed a right descending 360-degree turn. The airplane then proceeded in a northwesterly direction where at 0822:31, the last radar return with altitude was reported. The last radar target at 0822:43, was a primary only radar return.

PERSONNEL INFORMATION

According to Federal Aviation Administration (FAA) records, the pilot was issued a private pilot certificate with airplane single engine land rating on July 2, 2000. He was issued a third class medical certificate with no limitations on June 1, 2001. A review of FAA records indicated the pilot did not have any previous accident or incidents, or previous enforcement actions.

A review of the medical application for the June 2001 medical revealed he listed his total flight time as 292 hours. Further review of the application revealed the pilot checked the "yes" block in response to the question, "History of ...any conviction(s) involving driving while intoxicated by, while impaired by, or while under the influence of alcohol or a drug...."

Review of the pilot's driver license records revealed he was charged with driving under the influence (DUI) on May 9, 2001; he pleaded nolo contendere to the charge on October 4, 2001.

AIRCRAFT INFORMATION

The airplane was manufactured by Cessna Aircraft Company in 1999, as model 172S, and was designated serial number 172S8137. It was certificated in the normal and utility categories, and was equipped with a 180-horsepower Lycoming IO-360-L2A engine, and a fixed pitch McCauley propeller.

A review of the maintenance records revealed the airplane was last inspected on June 3, 2002, in accordance with an annual inspection. The airplane had accumulated 1.2 hours since the inspection at the time of the accident.

METEOROLOGICAL INFORMATION

A METAR weather observation taken from the Tampa International Airport (KTPA) on the day of the accident at 0753 (approximately 29 minutes before the accident), indicates the wind was calm, the visibility was 10 statute miles, scattered and overcast clouds existed at 13,000 and 25,000 feet, respectively, the temperature and dew point were 27 and 21 degrees Celsius, respectively, and the altimeter setting was 29.97 inHg. The accident site was located approximately 007 degrees and 9 nautical miles from KTPA.

COMMUNICATIONS

The pilot did not establish two way communications with any air traffic control facility. The common traffic advisory frequency (CTAF) at the Vandenberg Airport is not recorded.

WRECKAGE AND IMPACT INFORMATION

The airplane crashed in a wooded area located near a residential area. The accident site was located at 28 degrees 07.630 minutes North latitude and 082 degrees 31.522 minutes West longitude, or approximately 12 nautical miles and 310 degrees from the departure airport (Vandenberg Airport).

Examination of the accident site revealed damage to trees at decreasing heights. The main wreckage consisting of the upright fuselage, partially attached vertical stabilizer, and engine assembly was located approximately 68 feet from the first tree contact location. The descent angle between the first trees contacted and the location where the main wreckage came to rest was calculated to be approximately 40 degrees. Aircraft debris was located along the energy path which was oriented on a magnetic heading of 146 degrees. The first two identified trees contacted by the airplane were located 14 feet apart and left and right of a centerline when viewed from the center point of the trees to the main wreckage location. The first two trees contacted were at differing heights, with the tree to the left of the centerline damaged approximately 75 feet above g...

Data Source

Data provided by the National Transportation Safety Board (NTSB). For more information on this event, visit the NTSB Records Search website. NTSB# MIA02FA104