37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1158480 |
Time | |
Date | 201403 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | LBE.Airport |
State Reference | PA |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Light Transport |
Operating Under FAR Part | Part 91 |
Flight Phase | Descent |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Small Transport |
Flight Phase | Final Approach |
Flight Plan | IFR |
Person 1 | |
Function | First Officer Pilot Flying |
Qualification | Flight Crew Air Transport Pilot (ATP) Flight Crew Flight Instructor Flight Crew Multiengine Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 88 Flight Crew Total 11000 Flight Crew Type 3900 |
Person 2 | |
Function | Pilot Not Flying Captain |
Qualification | Flight Crew Air Transport Pilot (ATP) |
Experience | Flight Crew Last 90 Days 90 Flight Crew Total 7500 Flight Crew Type 260 |
Events | |
Anomaly | ATC Issue All Types Conflict Airborne Conflict Deviation - Procedural Published Material / Policy |
Miss Distance | Horizontal 2500 Vertical 1000 |
Narrative:
While on a shallow VMC descent into the lbe area; johnstown approach advised us of king air traffic at our 1-2 o'clock position. We advised 'traffic in sight' and the controller responded with 'maintain visual separation.' continuing our descent; the light twin also advised 'traffic in sight;' and again the controller responded with 'maintain visual separation on the jet.' while monitoring our TCAS display; I recognized the necessity to increase our rate of descent; but the system still barked an advisory command. It was evident that we were on a converging course; something not conveyed to us by the controller. Accepting the separation command; we essentially exonerated the controller of all responsibility. It would have been nice to know initially the degree of threat the light twin actually was. In the future I will not call traffic in sight descending into this area; relinquishing my protection. I'm surprised the controller did not advise the degree of threat posed by the twin.
Original NASA ASRS Text
Title: A Corporate jet crew and light twin pilot both asked JST Approach about mutual traffic and were told to maintain visual but neither was advised of their converging tracks which resulted in the jet crew taking evasive action.
Narrative: While on a shallow VMC descent into the LBE area; Johnstown Approach advised us of King Air traffic at our 1-2 o'clock position. We advised 'traffic in sight' and the Controller responded with 'maintain visual separation.' Continuing our descent; the light twin also advised 'traffic in sight;' and again the Controller responded with 'maintain visual separation on the jet.' While monitoring our TCAS display; I recognized the necessity to increase our rate of descent; but the system still barked an advisory command. It was evident that we were on a converging course; something NOT conveyed to us by the Controller. Accepting the separation command; we essentially exonerated the Controller of all responsibility. It would have been nice to know initially the degree of threat the light twin actually was. In the future I will NOT call traffic in sight descending into this area; relinquishing my protection. I'm surprised the Controller did not advise the degree of threat posed by the twin.
Data retrieved from NASA's ASRS site 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.