Editor:
If you have read some of my articles you know I have been an aviator for 60 years more or less; retiring a few years ago when I donated my Homebuilt RV-7A. During that time there were many ups and downs (pun intended). There were furloughs that lasted years, even so I accumulated some 18,000 plus or minus flight hours. So other jobs and career choices were necessary.
Some background concerning the midair that occurred at DCA, Ronald Reagan Washington National Airport. It appears to me that an American RJ Jet aircraft on final approach to Runway 33 was hit by an Army Sikorsky UH-60 Helicopter. (Black Hawk is a four-blade, twin-engine, medium-lift utility military helicopter ) Cable channel news has been covering this tragic accident almost 24/7. Various so called experts have attempted to inform. I hope to give some information to you readers that may not have been covered in the various newscasts. During the period of Ronald Reagan's Presidency, the Air Traffic Controllers union went on strike. President Reagan ordered them back to work or he would terminate their employment. I was furloughed from TWA (Trans World Airlines) at the time. I was a Flight Engineer on Boeing 727 aircraft. Air traffic route control centers and local airport towers we severely shorthanded; procedures had to be changed to accommodate the manpower shortage. One was to offer employment to furloughed airline pilots, another was to change some IFR rules (Instrument Flight Rules). One of these measures was to institute tower to tower IFR flight below Flight level 180 - eighteen thousand feet. So instead of Air Route Traffic Control (ATC) IFR aircraft were given IFR clearances from CID (Cedar Rapids) tower to a destination tower or many enroute tower until destination. I applied for an opening at the CID tower - Flight Data Aid. When qualified I would give stage three, tower to tower enroute clearances, ATIS reports (airport weather - temperature, altimeter setting, wind speed and direction, active runway, turbulence advisories, icing conditions, and NOTAMS --- Notices to Airmen, taxi closures or obstructions.) So I got to experience the other side of the microphone. It did not take long for me to realize, I did not have the aptitude to be a fully trained controller. However, I did learn many Air Traffic rules, restrictions, and proper language to use. To Witt: Normal procedure, ATC gives a "handoff" to Airport terminal Radar. The Terminal controller will give altitude and or heading to the final approach course - a command of "cleared for the approach" is given and a handoff is given to the Local Controller (tower operator), followed by a 'Cleared to Land" command. All these commands mean there is no other traffic on radar or visual that would jeopardize safety. In the DCA case the AA RJ was given a cleared to land command for Runway 33. Coming from the South means the RJ followed the Potomac River to a final approach. Information differs as the altitude where the midair occurred. The Radar sweep has the RJ at a different altitude than the flight recorder on the helio. That can be explained as the terminal radar antenna makes a 360 degree sweep every 3-4 seconds or more - so what the radar operator sees is a momentary snapshot of the RJ. There is discussion as to whether the helo pilot in command was using night vision goggles. That can be determined by examining the wreckage. I have never used them, but on one of my flights as Captain on The DC-9 I had an FAA inspector on board giving us a route check - and he was also an Air National Guard pilot on C-141 aircraft. In conversation he told us that they used these goggles at night flying at only 100 feet off the ground - good grief. One pilot had the goggles, the other cross checked the instruments and a visual outside. Do not know the Army procedure. Something went amiss either the helio was at the wrong altitude under the final approach path to RW 33 or the Local missed the conflict. Whatever, The midair occurred and many lives were lost. It will take the accident investigators months of examination to determine the probable cause. It looks to me that 1. The helio should not have been in that location proper altitude or no. 2. The helicopter pilot(S) should have visually seen the conflict and taken evasive action; then all lived and a "near miss" would have been reported to proper authority.
While I was still a line pilot for TWA a new device was installed - TCAS - a traffic alert system. The indicator was on the instrument panel; when an aircraft came close to our path and altitude It would give "Traffic, Traffic" alert. On the instrument a blip would appear, usually the blip would be at the 9 to 3 o'clock position. If a conflict was detected it would give a "climb, climb or descend, descend" command. Of course that was 24 plus years ago so no doubt the TCAS system is much better then when I was flying airliners. A question would be was the TCAS operational on the RJ. If so it should have given ample warning for the RJ to institute a "missed approach", commonly called a "go-around". All saved.
One other note: The aircraft I built had the required nav lights, red on one wing, green on the other with a white tail light on the horizontal Stabilizer below the vertical stabilizer; also I had strobe lights, a high intensity white flash seconds apart. Every airliner I flew had this system with an addition of a rotating beacon on the underside of the fuselage; a high intensity red light. I am sure the RJ (regional jet) had the same system. I cannot understand how the helio crew did not seet the RJ at least a mile from their position and make corrective action then! As an aside the nav light system I installed was not cheap, but money may be easier to earn than the pain and maybe death of a collision. In addition I installed the system and wiring to the controller. But hooked the wires opposite to required; shorted the controller out so ship to the manufacture, Whelan, for repair. Of course it was not a manufactured error so I had to pay for the shipping and repair. Education no matter how gained is costly. Preserve, adapt, overcome.
Sorry for the length of the article, but I hope you who have no aviation experience have a perspective on what did happen and what should have happened.
https://www.fly.faa.gov/Information/east/zdc/dca/00443AD.PDF DCA airport diagram
Regards and blessings,
John Stiegelmeyer Capt. TWA (Ret)
Comments
Submit a CommentPlease refresh the page to leave Comment.
Still seeing this message? Press Ctrl + F5 to do a "Hard Refresh".
During my time in the Infantry I flew on many Blackhawks in both day and night operations. When the pilots started using PVS-5 Night Vision Goggles they were never intended to be used by pilots of aircraft. While they were great for night vision, it was difficult to judge depth perception. Nevertheless Army pilots began to train with them during nighttime training missions. While most pilots became very good at flying at night with night vision, there were still a series of mishaps due to the pilot misjudging the contours of the earth at combat speeds while flying nap of the earth where there is little margin for error. Flying nap of the earth in a Blackhawk is usually just above tree top level, dropping into valleys and sharply climbing over the terrain. In the video that has been shown by the press, it appeared that the UH-60 was not flying nap of the earth as it appeared to be far above what has been my experiences. It is a horrible accident that should not have happened. It's painful to know the families that are now suffering the loss of their loved ones. I will say that the Blackhawk pilots are some of the best trained pilots in the world for their craft and they are very good at what they do. I suspect this may come down to a problem with human error in the control tower. For now we should all pray for the families of all the victims, civilian and military.
Thanks for the info. This particular Aviation Battalion has been reported as one of the best trained. Their job is transporting VIPs from various locations to the Pentagon. As the NTSB investigation proceeds we will get to a probable cause
While at the flight data aid job my position was between the ground controller and Local. On a few occasions there would be and urgent call on intercom for me to haul ass to the terminal radar room. They needed help right now. They termed this "going down the sh**er". One can only talk so fast and control only so many aircraft. My only assistance was to tear off flight plan strips from the FDEP machine determine if it a fly over or a lander annotate such and give it to the proper sector controller - North or South. I would stack the strips properly at the proper controller position. Things could go from routine to panic in short order.
As an aside: On Active Duty Air Force we were deployed to Madrid Spain. I was copilot on KC-135 tanker. We were heading west at FL 300 or more and then had a turn south we did not change to the proper hemispherical altitude (East is Least, West is best). I estimate the distance at approx. 10 miles - I saw smoke; exhaust from jet engines. At our speed the closure rate was fast. I rapidly recognize the aircraft was at our altitude, the likely hood of a collision was high. I shouted to the Air Craft Commander to "Break Left, Break left". As in a commanding voice as I could. He did not turn. Fortunately the Airliner took evasive action. We had a high HQ officer on board - I got my ass chewed because I did not make a near miss report. Well Gooolly! we had survived, Sharon has a live husband. I took the ass chewing without comment. Go figure.
Regards,
John Stiegelmeyer
Thanks for the comments and information. This particular aviation battalion is reported to be one of the best by all measures. My data aid position was between grd and local with the radar downstairs. Many times I was ordered to the radar as the two sector controllers were close to being overwhelmed.