37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 557227 |
Time | |
Date | 200208 |
Day | Wed |
Local Time Of Day | 1201 To 1800 |
Place | |
Locale Reference | navaid : eno.vortac |
State Reference | DE |
Altitude | msl single value : 5000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Operator | common carrier : air carrier |
Make Model Name | Do 328 TP (Turboprop) |
Operating Under FAR Part | Part 121 |
Navigation In Use | other |
Flight Phase | descent : approach |
Route In Use | arrival : on vectors |
Flight Plan | IFR |
Aircraft 2 | |
Operator | common carrier : air carrier |
Make Model Name | Dash 8 Series Undifferentiated or Other Model |
Operating Under FAR Part | Part 121 |
Flight Plan | IFR |
Person 1 | |
Affiliation | company : air carrier |
Function | flight crew : captain oversight : pic |
Qualification | pilot : atp pilot : multi engine pilot : instrument pilot : cfi |
Experience | flight time last 90 days : 240 flight time total : 8000 flight time type : 4200 |
ASRS Report | 557227 |
Person 2 | |
Affiliation | company : air carrier |
Function | flight crew : first officer |
Qualification | pilot : commercial pilot : cfi pilot : multi engine pilot : instrument |
Experience | flight time last 90 days : 240 flight time total : 2100 flight time type : 1300 |
ASRS Report | 557226 |
Events | |
Anomaly | conflict : airborne critical non adherence : far non adherence : required legal separation non adherence : published procedure other anomaly other |
Independent Detector | aircraft equipment : tcas other flight crewa other flight crewb |
Resolutory Action | flight crew : took evasive action none taken : detected after the fact other |
Consequence | faa : reviewed incident with flight crew other |
Miss Distance | horizontal : 12000 vertical : 700 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Air Traffic Incident | Inter Facility Coordination Failure Operational Error |
Narrative:
I was PIC and PNF of flight from gsp-phl. On this date we experienced an RA just north of eno VOR turning to join V29. Our flight planned route and last cleared was eno V29 dqo phl. We were working with ZDC and after some vectoring for descent, we were cleared direct eno and to contact dover AFB approach. Dover approach cleared us to 5000 ft and we leveled at 5000 ft to the southwest of eno. At eno I, the PNF, went to communication #2 to contact phl operations for gate, etc. As the aircraft turned to join V29 we received a TA on traffic at our 10 O'clock position and approximately 6 mi. As I finished with company I was searching for the traffic. As I returned to communication #1, still searching for the traffic, I was about to query dover AFB approach about the traffic when we received an RA to descend. The traffic now about 2.5 mi. The first officer and PF complied with the RA and started a descent. Dover approach then called traffic and told us to turn to a heading of 090 degrees. I then informed them of our RA compliance and we had a visual about the time we reached 4300 ft. We then started a climb back to our assigned altitude of 5000 ft. Dover AFB then queried our last route cleared but before we could answer they handed us off to the phl approach. After all was settled I called back to dover AFB approach on communication #2 and inquired about the RA. They said ZDC showed us cleared eno V157 ood phl. I told them this was not the case and we were never given new routing. This difference caused us to turn to join V29 the eno 360 degree radial instead of what dover thought we would do which was join V157 the 031 degree radial off eno. Our larger turn brought us too close to the dash-8 traffic and we received an RA. Dover AFB approach said traffic almost always goes to ood after eno on V157 and in the future to verify routing. To minimize future problems, I contacted company dispatch and they have changed the company's preferred route to reflect ric V16 eno V157 ood phl for southwest arrs to phl. Supplemental information from acn 557226: my captain returned to dover approach to sort out the problem on the second radio. I learned later that he (dover approach) was informed ZDC had given us the reroute. The captain nor myself do not recall receiving a reroute from anyone concerning the portion of the flight in question as we would have written the reroute down on the notepad and read the route verbally to the controller.
Original NASA ASRS Text
Title: D328 CREW AND A DH8 HAD LESS THAN LEGAL SEPARATION IN DOV MIL CLASS D.
Narrative: I WAS PIC AND PNF OF FLT FROM GSP-PHL. ON THIS DATE WE EXPERIENCED AN RA JUST N OF ENO VOR TURNING TO JOIN V29. OUR FLT PLANNED RTE AND LAST CLRED WAS ENO V29 DQO PHL. WE WERE WORKING WITH ZDC AND AFTER SOME VECTORING FOR DSCNT, WE WERE CLRED DIRECT ENO AND TO CONTACT DOVER AFB APCH. DOVER APCH CLRED US TO 5000 FT AND WE LEVELED AT 5000 FT TO THE SW OF ENO. AT ENO I, THE PNF, WENT TO COM #2 TO CONTACT PHL OPS FOR GATE, ETC. AS THE ACFT TURNED TO JOIN V29 WE RECEIVED A TA ON TFC AT OUR 10 O'CLOCK POS AND APPROX 6 MI. AS I FINISHED WITH COMPANY I WAS SEARCHING FOR THE TFC. AS I RETURNED TO COM #1, STILL SEARCHING FOR THE TFC, I WAS ABOUT TO QUERY DOVER AFB APCH ABOUT THE TFC WHEN WE RECEIVED AN RA TO DSND. THE TFC NOW ABOUT 2.5 MI. THE FO AND PF COMPLIED WITH THE RA AND STARTED A DSCNT. DOVER APCH THEN CALLED TFC AND TOLD US TO TURN TO A HEADING OF 090 DEGS. I THEN INFORMED THEM OF OUR RA COMPLIANCE AND WE HAD A VISUAL ABOUT THE TIME WE REACHED 4300 FT. WE THEN STARTED A CLB BACK TO OUR ASSIGNED ALT OF 5000 FT. DOVER AFB THEN QUERIED OUR LAST RTE CLRED BUT BEFORE WE COULD ANSWER THEY HANDED US OFF TO THE PHL APCH. AFTER ALL WAS SETTLED I CALLED BACK TO DOVER AFB APCH ON COM #2 AND INQUIRED ABOUT THE RA. THEY SAID ZDC SHOWED US CLRED ENO V157 OOD PHL. I TOLD THEM THIS WAS NOT THE CASE AND WE WERE NEVER GIVEN NEW ROUTING. THIS DIFFERENCE CAUSED US TO TURN TO JOIN V29 THE ENO 360 DEG RADIAL INSTEAD OF WHAT DOVER THOUGHT WE WOULD DO WHICH WAS JOIN V157 THE 031 DEG RADIAL OFF ENO. OUR LARGER TURN BROUGHT US TOO CLOSE TO THE DASH-8 TFC AND WE RECEIVED AN RA. DOVER AFB APCH SAID TFC ALMOST ALWAYS GOES TO OOD AFTER ENO ON V157 AND IN THE FUTURE TO VERIFY ROUTING. TO MINIMIZE FUTURE PROBS, I CONTACTED COMPANY DISPATCH AND THEY HAVE CHANGED THE COMPANY'S PREFERRED RTE TO REFLECT RIC V16 ENO V157 OOD PHL FOR SW ARRS TO PHL. SUPPLEMENTAL INFO FROM ACN 557226: MY CAPT RETURNED TO DOVER APCH TO SORT OUT THE PROB ON THE SECOND RADIO. I LEARNED LATER THAT HE (DOVER APCH) WAS INFORMED ZDC HAD GIVEN US THE REROUTE. THE CAPT NOR MYSELF DO NOT RECALL RECEIVING A REROUTE FROM ANYONE CONCERNING THE PORTION OF THE FLT IN QUESTION AS WE WOULD HAVE WRITTEN THE REROUTE DOWN ON THE NOTEPAD AND READ THE RTE VERBALLY TO THE CTLR.
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.