# NTSB NYC94FA119: Cessna 172RG, N6624R, Kiptopeka, VA, July 11, 1994 - Type: NTSB accident investigation - Classification: Accident · Fatal · Field investigation · Final report - Date: July 11, 1994, 16:18 local (20:18 UTC) - Place: Kiptopeka, VA - Coordinates: 37.259098, -76.490554 (estimated) - Nearby events: https://openairdocs.org/map.md?lat=37.2591&lon=-76.4906&mi=10 - Phase of flight: [Maneuvering](https://openairdocs.org/ntsb-phases/450) (OpenAirDocs' grouping) - Highest injury: Fatal - Injuries: 1 fatal, 4 uninjured - Status: Completed, report August 1, 1995 - Report: Approved by Office Director - NTSB case key (mKey): 38676 - NTSB case page: https://web.ntsb.gov/investigations/?ntsbnumber=NYC94FA119 - NTSB report (PDF, downloads): https://data.ntsb.gov/carol-repgen/api/Aviation/ReportMain/GenerateNewestReport/38676/pdf - Page: https://openairdocs.org/ntsb/NYC94FA119 ## Probable cause (aircraft 2) 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. ## Probable cause (aircraft 1) 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 In NTSB's coding before 2008 (https://www.ntsb.gov/GILS/Documents/codman.pdf). - Midair collision, maneuvering - visual lookout - inadequate, pilot of other aircraft (cause) - traffic advisory - not issued, atc personnel(dep/apch) (contributing factor) - In flight collision with terrain/water, descent - uncontrolled - Midair collision, maneuvering - turn to reverse direction - visual lookout - inadequate, pilot in command (cause) - traffic advisory - not issued, atc personnel(dep/apch) (contributing factor) ## Analysis (aircraft 2) 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. ## Analysis (aircraft 1) 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 (aircraft 2) SEE NARRATIVE FOR FILE NYC94FA119A. ## Factual narrative (aircraft 1) 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 1 - Registration: [N6624R](https://openairdocs.org/deregistered/N6624R-1994-09-01), registration cancelled 1994-09-01, S/N 172RG0219 (OpenAirDocs) - Reported make and model: CESSNA 172RG - Registry model: [Cessna 172RG](https://openairdocs.org/model/cessna-172rg) (registry code 2072438) (OpenAirDocs) - Category: Airplane - Serial number: 172RG0219 - Airframe hours: 2650 - Engines: 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 ## Aircraft 2 - Registration: N62505 (not matched to a registry record) - Reported make and model: Sikorsky MH-53E - Category: Helicopter - Serial number: 162505 - Airframe hours: 2055 - Engines: GE T64-GE-416 4380 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 As NTSB recorded them. NTSB leaves out names. - Pilot, aircraft N6624R; age 62; 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 - Pilot, aircraft N62505; age 29; 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 (OpenAirDocs). - [Accident 19940711018131A](https://openairdocs.org/incident/19940711018131A), Jul 11, 1994: Cessna 172RG, Kiptopeka, VA, Destroyed, 1 fatal. Fish spotting on radar discreet code. Was struck from above and behind by military copter. ATC failed alert pilot. - [Accident 19940711018132A](https://openairdocs.org/incident/19940711018132A), Jul 11, 1994: Kiptopeka, VA, Substantial damage. Military copter on test flight on 1200 code descending. Collided from above, rear with fish spotter. Landed safely. From the NTSB's public API. Aircraft are matched to registry aircraft by N-number and event date, checked against the reported serial number, make and model; the registry's history has gaps, so older matches can be wrong. Compare the reported make and model. --- OpenAirDocs.org is an independent research project of [Contrail Labs](https://contraillabs.com/). It is not affiliated with the FAA or the NTSB. Source documents are U.S. government works in the public domain.