NYC94FA119

NTSB accident investigation · Cessna 172RG · Kiptopeka, VA · July 11, 1994

Accident · FatalField investigationFinal report
Date
July 11, 1994, 16:18 local (20:18 UTC)
Place
Kiptopeka, VA
Injuries
1 fatal, 4 uninjured
Phase of flight
Maneuvering
Aircraft
N6624RCessna 172RGN62505Sikorsky MH-53E
Weather
Visual (VMC) · Day
Status
Completed · report August 1, 1995
Report
Approved by Office Director
Case key
38676

From the NTSB’s public API. By law, NTSB reports can’t be used as evidence in lawsuits over the accident.

On this page

Probable cause

Inadequate visual lookout by the flightcrew of the helicopter. A factor related to the accident was: failure of the departure controller to issue a traffic advisory.

Inadequate visual lookout by the flightcrew of the helicopter. A factor related to the accident was: failure of the departure controller to issue a traffic advisory.

Sequence of events

NTSB’s coding before 2008: each occurrence and phase of flight, and the causes and factors under it. The codes are defined in NTSB’s coding manual.

Midair collisionManeuvering
Visual lookout - inadequatePilot of other aircraftCause
Traffic advisory - not issuedAtc personnel(dep/apch)Factor
In flight collision with terrain/waterDescent - uncontrolled
Midair collisionManeuvering - turn to reverse direction
Visual lookout - inadequatePilot in commandCause
Traffic advisory - not issuedAtc personnel(dep/apch)Factor

Analysis

A Cessna 172RG, N6624R, was on a flight to spot fish from about 3500' MSL. In the same vicinity, a navy sikorksy MH-53A helicopter was on a maintenance test flight. They collided in midair over the chesapeake bay, near Kiptopeka, VA. The 172RG went into an uncontrolled descent & crashed in the bay; the helicopter was landed in a field. Investigation revealed that the 172RG pilot had contacted the DR-1 controller at norfolk departure control (ATC) at 1458 EDT. He was assigned a transponder code & was receiving VFR flight following. The helicopter pilot was not in contact with ATC & was using a VFR transponder code of 1200. Two controller changes occurred at the DR-1 position after N6624R established contact. At 1610 EDT, the 2nd controller gave a relief briefing to the 3rd controller & referenced the 172RG. The helicopter had been operating at about 500'; the pilot then made a climb (momentarily) to about 6000' to test a fuel dumping system. Radar data showed the helicopter then entered a descent & was turning when it converged on the 172RG from above & behind. At about 1618, the midair collision occurred about 3500' MSL. There had been no communication between ATC & the 172RG pilot for about 33 minutes before the collision.

A Cessna 172RG, N6624R, was on a flight to spot fish from about 3500' MSL. In the same vicinity, a navy sikorksy MH-53A helicopter was on a maintenance test flight. They collided in midair over the chesapeake bay, near Kiptopeka, VA. The 172RG went into an uncontrolled descent & crashed in the bay; the helicopter was landed in a field. Investigation revealed that the 172RG pilot had contacted the DR-1 controller at norfolk departure control (ATC) at 1458 EDT. He was assigned a transponder code & was receiving VFR flight following. The helicopter pilot was not in contact with ATC & was using a VFR transponder code of 1200. Two controller changes occurred at the DR-1 position after N6624R established contact. At 1610 EDT, the 2nd controller gave a relief briefing to the 3rd controller & referenced the 172RG. The helicopter had been operating at about 500'; the pilot then made a climb (momentarily) to about 6000' to test a fuel dumping system. Radar data showed the helicopter then entered a descent & was turning when it converged on the 172RG from above & behind. At about 1618, the midair collision occurred about 3500' MSL. There had been no communication between ATC & the 172RG pilot for about 33 minutes before the collision.

Factual narrative

See narrative for file NYC94FA119A.

On July 11, 1994, about 1618 eastern daylight time, a Cessna 172RG, N6624R (call sign "Spotter 24R), piloted by Mr. William Sklar, and a United States Navy, Sikorsky MH-53E helicopter, 162505 (call sign Vulcan 555), piloted by two Navy pilots, and two crew members, collided in midair while maneuvering over the water near Kiptopeka, Virginia.

The Cessna impacted into approximately 10 feet of water, and was destroyed. The Navy Helicopter proceeded in a northbound direction and landed without further incident in a field approximately 2 miles north of the collision site. The helicopter was substantially damaged. The pilot of Cessna was fatally injured. There was no injuries to any of the crew members on the Navy Helicopter. Visual meteorological conditions prevailed and no flight plan had been filed by the Cessna. The Cessna flight was being conducted under 14 CFR 91.

The Cessna was operating as a fish spotting aircraft, and was receiving flight following from Norfolk Departure Control Radar, number one facility (DR-1), Norfolk, Virginia, and was given an assigned transponder code of 0171. There was no radio communication between DR-1, and Cessna N6624R for approximately 33 minutes prior to the collision.

The Navy helicopter had departed Chambers Field, Naval Air Station (NAS), Norfolk, and was conducting maintenance tests. The helicopter was on a military flight plan, and was not in radio contact with DR-1, using a VFR transponder code of 1200. The helicopter had ascended to approximately 6000 feet MSL, completed a maintenance test, and started a descending left turn.

The helicopter was in a descending left turn when the mid-air collision occurred.

According to the written statement of Navy, Lieutenant (Lt.) James Rocha, the pilot of the Navy Helicopter:

The weather was clearest near the tip of the Cape Charles peninsula. We climbed to 6000' in an orbit over the water off to the west of the peninsula...we completed the dump test after just a minute or two and I initiated a descent. I was descending in a left orbit over the water to the west of the peninsula. As we turned through the east, perpendicular to the shore, I noted civilian traffic at the 12 o'clock position, low, a few miles out. The copilot stated she had the traffic in sight and the crew chief stated that lookouts were posted. I continued the left orbit descending at approximately 1000' per minute. As I turned through a north-easterly heading on the next orbit, I heard and felt the impact.

Lt. Rocha wrote that he did not know he had impacted with an airplane, until he asked his crew and the copilot told him what happened. He then executed an emergency autorotational descent, changed the transponder code 7700 (emergency), and landed.

According to the copilot, Lt. Shari Beeth's statement, as the helicopter turned towards land she, "...spotted a small civilian aircraft over [the] land approximately 4 miles out, much lower... and not headed in our general direction." Lt. Beeth told the pilot she saw the traffic, and according to her statement, they continued in a left descending turn "for 1 or 2 full rotations." Lt. Beeth wrote:

...then as we turned away from land again [west], I caught a glimpse of something out the corner of my eye. I jerked my head to the right and saw a civilian aircraft just prior to it impacting us on our aft starboard [right] side. The aircraft appeared to be in a climbing left turn. I did not actually see it hit us as I had snapped my head back toward the front to grab the controls in an effort to take evasive maneuvers....

According to the NTSB ATC, Group Chairman's report, N6624R was handed off from Oceana Naval Air Station to the Arrival Radar one (AR-1) controller at 1457:50. The AR-1 controller initiated an automated handoff on N6624R to the DR-1 (Departure radar-one controller)controller. N6624R contacted the DR-1 controller at 1458:06, saying "with you Cape Henry at three point five for Lynnhaven." The controller told the aircraft to "ident" and then issued an altimeter setting of 30.12.

At 1408:01, N6624R informed the controller that he would like to proceed west to the Hampton tunnel area. About 5 minutes later, the controller called traffic to Continental 1552, saying that there was traffic three miles north, orbiting, "a Cessna spotting fish at 3,500." The controller then informed N6624R about a Boeing 737 climbing to 3,000 ft. N6624R transmitted "in the blind," "Two four Romeo is watching traffic." The DR-1 controller replied, "thanks."

At 1516:16, the DR-1 controller called traffic to N6624R which was a Boeing 737 leaving 2,000 feet for 4,000 feet. Ten minutes later, at 1526:04, N6624R told the DR-1 controller that he was "going to the York River, sir."

At 1537:20, the DR-1 controller gave a relief briefing to the next controller whose operating initials were LS. N6624R was not included in the briefing. At 1545:01, N6624R transmitted that he was eastbound towards Cape Charles, and then he would be working his way south toward the "high span." The DR-1 controller then inquired what the call sign was of the fish spotter. N6624R replied, "uh two four Romeo." The DR-1 controller then transmitted, "Fish Spotter two four Romeo, Norfolk altimeter three zero one one, ident."

The DR-1 controller, at 1550:36, pointed out "Fish Spotter two four Romeo" to the Peninsula radar controller (PSR) and the East Feeder radar controller. Both of the adjacent radar sectors approved the point out.

At 1610:11, the DR-1 controller gave a relief briefing to DK, and N6624R was mentioned. He said, "...you have one fish spotter, P and E (Peninsula Radar and East Feeder Radar) are watching at thirty five, going up and down for the high span." (The operating initials of the controller leaving the sector were LS and the initials of the controller taking over the sector were DK).

The precise time of the accident according to the NTSB RECORDED RADAR STUDY was 1618:30 (2018:30 UTC). From the time of the above relief briefing for DK to the time of the accident, there was no communication between N6624R and the DR-1 controller. By reference to the RECORDED RADAR STUDY beginning at 1610:00 (2010:00 UTC), both aircraft remained in the general vicinity of each other until the accident occurred. The helicopter, designated by a diamond symbol, climbed through the altitude of N6624R (which was 3500 ft), and leveled off for about 7 radar "hits" at 5,800 ft. The helicopter then began a continuous descent to 3500 ft, where the collision took place. The accident occurred at 1618:30. The helicopter continued descent and landed.

At 1639:42, the DR-1 controller transmitted, "Fish spotter two four Romeo, you still out there?" There were no replies. Operation at that sector continued. N6270V, a fishspotter, called at 1652:37, and asked, "...what can you tell me about the Cessna and helicopter crash down at the bay there?" The DR-1 controller then asked N6270V what his position was. N6270V said that his position was "about forty seven north," and told the controller that he heard a Cessna and a helicopter crashed, and that 24 Romeo could not be contacted. He then asked if the DR-1 controller had been working him. The DR-1 controller replied, " Sir, I don't have any information on that right now, they're investigating it. I have no information to pass on to you. I know it's one of your comrades, I'd sure love to say something to you, but I have no information whatsoever, right now." N6270V thanked the controller, and then asked it if there would be any information available later. Thirty seconds later, N6270V transmitted that he was wondering if the controller had been working spotter two four Romeo. The DR-1 controller replied, "... that's affirmative, we were working two Four R

Aircraft · 2

Registration
N6624R
Reported as
Cessna 172RG
Category
Airplane
Serial number
172RG0219
Airframe hours
2,650
Engine
Lycoming O-360-F1A6, 180 horsepower, reciprocating
Damage
Destroyed
Flight
Part 91
Registered owner
William Sklar
Airworthiness certificate
Standard, Normal
Last inspection
Annual · July 16, 1994 · 10 hours before
Departed
PVG · Portsmouth, VA

Matched to the registry by N-number and the event date; the registry’s history has gaps, so older matches can be wrong. Compare the reported make and model.

Registration
N62505
Reported as
Sikorsky MH-53E
Category
Helicopter
Serial number
162505
Airframe hours
2,055
Engine
GE T64-GE-416, 4,380 horsepower, turbo shaft
Damage
Substantial damage
Flight
Public use
Operator
US Navy
Registered owner
Department Of The Navy
Airworthiness certificate
Standard, Transport
Last inspection
Continuous airworthiness · July 7, 1994
Departed
NGU · Nas Norfolk, VA
Flight plan
Military VFR

Flight crew · 2

As NTSB recorded them. NTSB leaves out names.

Role
Pilot, aircraft N6624R
Age
62
Certificate
Commercial
Airplane ratings
Multi-engine land, Single-engine land
Instrument ratings
Airplane
Medical
Class 2, Valid Medical--w/ waivers/lim
Seat
Left
Toxicology
Performed
Flight hours
40,000 total · 10,774 in this make and model · 38,774 as pilot in command · 474 in the last 90 days · 72 in the last 30 days · 10 in the last 24 hours
Role
Pilot, aircraft N62505
Age
29
Certificate
Military
Airplane ratings
Single-engine land
Instrument ratings
Helicopter
Medical
Class 1, Valid Medical--no waivers/lim.
Seat
Left
Flight hours
948 total · 714 in this make and model · 285 as pilot in command · 57 in the last 90 days · 29 in the last 30 days

Weather

Conditions
Visual (VMC) · Day
Wind
30° at 7 knots
Visibility
10 statute miles
Lowest ceiling
25,000 ft broken
Temperature
82 °F, dew point 66 °F
Altimeter
30.00 inHg
Observed at
ORF, 18 nm away

FAA reports on this event · 2

The FAA’s own accident and incident reports, matched to the aircraft by N-number and date.