37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 356992 |
Time | |
Date | 199610 |
Day | Mon |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | atc facility : fqm |
State Reference | PA |
Altitude | msl bound lower : 14000 msl bound upper : 14000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Commercial Fixed Wing |
Operating Under FAR Part | Part 135 |
Navigation In Use | Other Other |
Flight Phase | cruise other |
Route In Use | enroute airway : zny |
Flight Plan | IFR |
Aircraft 2 | |
Operator | other |
Make Model Name | Thunderbolt II (Warthog A-10) |
Operating Under FAR Part | other : other |
Flight Phase | cruise other |
Flight Plan | VFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 250 flight time total : 2500 flight time type : 400 |
ASRS Report | 356992 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : instrument pilot : commercial |
Events | |
Anomaly | conflict : airborne less severe non adherence : far other anomaly other |
Independent Detector | aircraft equipment other aircraft equipment : unspecified other controllera other flight crewa |
Resolutory Action | flight crew : took evasive action |
Consequence | Other |
Miss Distance | horizontal : 1000 vertical : 100 |
Supplementary | |
Primary Problem | Flight Crew Human Performance |
Air Traffic Incident | Pilot Deviation |
Narrative:
Approximately 5 mins after leveling off at cruise altitude, ATC called out VFR traffic to the first officer while I was off the radios making a routine passenger briefing. When I returned to the radio frequency the first officer pointed to traffic displayed on the TCASII display. The traffic was just inside the 20 mi range at 500 ft above our altitude. The first officer informed me that ATC told her the traffic was northbound (we were wbound), however, the traffic on the TCASII appeared to be moving east. Due to the distance from the traffic I could not acquire them visually. After visually searching for the traffic, (it was at the 10-11 O'clock position) I began to attend to other PNF duties, ie, looking at the charts and tuning radios. About 5 mins after the TA from ATC, (there were no subsequent advisories) the TCASII provided a traffic warning for an aircraft at 9 O'clock and +500 ft. I visually acquired the aircraft at 500 ft above and saw that it was an A10 after which I saw another in loose formation trailing the lead at about 100 ft above us. The first officer also saw the formation aircraft and began a descent. At that moment the wingman turned parallel to our course and dropped behind us while the formation leader passed overhead. The conflict was caused by the wingman (with his transponder/encoder turned off) flying several hundred ft lower than the lead aircraft. ATC had no way of knowing this would cause a conflict since they only saw and spoke with the leader who was at the proper altitude. In the future I would recommend greater separation (vertically) from formation flts since only 1 of the aircraft is in radar contact. From now on I will have a greater awareness of the other aircraft in a formation flight when a formation is called out as a potential traffic conflict.
Original NASA ASRS Text
Title: 2 MIL A10'S IN FORMATION FLT PASS IN CLOSE PROX TO A COMMUTER ACFT AT 14000 FT. TFC WAS ISSUED ON 1 MIL ACFT OBSERVED ON TCASII. THE COMMUTER PLT SAW THE SECOND A10 WITHOUT AN OPERATING XPONDER BEHIND AND BELOW THE LEAD ACFT. THEY PASSED WITHIN 1000 FT OF EACH OTHER.
Narrative: APPROX 5 MINS AFTER LEVELING OFF AT CRUISE ALT, ATC CALLED OUT VFR TFC TO THE FO WHILE I WAS OFF THE RADIOS MAKING A ROUTINE PAX BRIEFING. WHEN I RETURNED TO THE RADIO FREQ THE FO POINTED TO TFC DISPLAYED ON THE TCASII DISPLAY. THE TFC WAS JUST INSIDE THE 20 MI RANGE AT 500 FT ABOVE OUR ALT. THE FO INFORMED ME THAT ATC TOLD HER THE TFC WAS NBOUND (WE WERE WBOUND), HOWEVER, THE TFC ON THE TCASII APPEARED TO BE MOVING E. DUE TO THE DISTANCE FROM THE TFC I COULD NOT ACQUIRE THEM VISUALLY. AFTER VISUALLY SEARCHING FOR THE TFC, (IT WAS AT THE 10-11 O'CLOCK POS) I BEGAN TO ATTEND TO OTHER PNF DUTIES, IE, LOOKING AT THE CHARTS AND TUNING RADIOS. ABOUT 5 MINS AFTER THE TA FROM ATC, (THERE WERE NO SUBSEQUENT ADVISORIES) THE TCASII PROVIDED A TFC WARNING FOR AN ACFT AT 9 O'CLOCK AND +500 FT. I VISUALLY ACQUIRED THE ACFT AT 500 FT ABOVE AND SAW THAT IT WAS AN A10 AFTER WHICH I SAW ANOTHER IN LOOSE FORMATION TRAILING THE LEAD AT ABOUT 100 FT ABOVE US. THE FO ALSO SAW THE FORMATION ACFT AND BEGAN A DSCNT. AT THAT MOMENT THE WINGMAN TURNED PARALLEL TO OUR COURSE AND DROPPED BEHIND US WHILE THE FORMATION LEADER PASSED OVERHEAD. THE CONFLICT WAS CAUSED BY THE WINGMAN (WITH HIS XPONDER/ENCODER TURNED OFF) FLYING SEVERAL HUNDRED FT LOWER THAN THE LEAD ACFT. ATC HAD NO WAY OF KNOWING THIS WOULD CAUSE A CONFLICT SINCE THEY ONLY SAW AND SPOKE WITH THE LEADER WHO WAS AT THE PROPER ALT. IN THE FUTURE I WOULD RECOMMEND GREATER SEPARATION (VERTLY) FROM FORMATION FLTS SINCE ONLY 1 OF THE ACFT IS IN RADAR CONTACT. FROM NOW ON I WILL HAVE A GREATER AWARENESS OF THE OTHER ACFT IN A FORMATION FLT WHEN A FORMATION IS CALLED OUT AS A POTENTIAL TFC CONFLICT.
Data retrieved from NASA's ASRS site as of July 2007 and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.