37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 618974 |
Time | |
Date | 200405 |
Day | Thu |
Local Time Of Day | 0601 To 1200 |
Place | |
Locale Reference | airport : ttn.airport |
State Reference | NJ |
Altitude | msl single value : 2000 |
Environment | |
Flight Conditions | VMC |
Light | Daylight |
Aircraft 1 | |
Controlling Facilities | tracon : phl.tracon |
Operator | common carrier : air taxi |
Make Model Name | King Air 100 A/B |
Operating Under FAR Part | Part 91 |
Flight Phase | climbout : intermediate altitude |
Route In Use | departure : on vectors |
Flight Plan | VFR |
Aircraft 2 | |
Controlling Facilities | tracon : phl.tracon |
Make Model Name | Small Aircraft, Low Wing, 2 Eng, Retractable Gear |
Flight Phase | cruise : level |
Person 1 | |
Affiliation | company : corporate |
Function | flight crew : first officer |
Qualification | pilot : multi engine pilot : instrument pilot : commercial |
Experience | flight time last 90 days : 100 flight time total : 1600 flight time type : 500 |
ASRS Report | 618974 |
Person 2 | |
Affiliation | company : corporate |
Function | flight crew : captain oversight : pic |
Events | |
Anomaly | conflict : airborne less severe non adherence : published procedure |
Independent Detector | atc equipment other atc equipment : radar/mode c other controllera other flight crewa |
Resolutory Action | controller : issued advisory |
Miss Distance | horizontal : 5000 vertical : 500 |
Supplementary | |
Problem Areas | ATC Human Performance |
Primary Problem | ATC Human Performance |
Narrative:
Departed IFR from ttn. At 1500 ft in VFR conditions on top. Cancelled IFR with phl departure. Controller advised traffic at 11 O'clock position, 3000 ft. I called 'looking for traffic.' controller called back, 'traffic less than 1 mi, 11 O'clock position.' I called traffic 'not in sight.' controller then called 'previously called traffic, traffic alert, 11 O'clock position, correction 1 O'clock position.' I called traffic in sight, determined traffic did not pose an imminent hazard. Controller called back and stated that I caused a conflict. I advised controller traffic not a hazard, however confusion was caused by her incorrect call, twice, of the traffic at 11 O'clock position, when it was actually at 1 O'clock position. Controller stated, 'but I corrected it to 1 O'clock position.' I already had traffic in sight at that point because I looked elsewhere when I did not see it at position called. I believe this error occurred due to spatial orientation confusion on part of controller and cannot suggest ways to prevent a recurrence, short of additional training.
Original NASA ASRS Text
Title: PHL APCH CTLR INCORRECTLY ISSUES TFC TWICE AT 11 O'CLOCK POS TO A BE10 PLT ON AN ACFT THAT WAS ON A CONVERGING COURSE AT 1 O'CLOCK POS.
Narrative: DEPARTED IFR FROM TTN. AT 1500 FT IN VFR CONDITIONS ON TOP. CANCELLED IFR WITH PHL DEP. CTLR ADVISED TFC AT 11 O'CLOCK POS, 3000 FT. I CALLED 'LOOKING FOR TFC.' CTLR CALLED BACK, 'TFC LESS THAN 1 MI, 11 O'CLOCK POS.' I CALLED TFC 'NOT IN SIGHT.' CTLR THEN CALLED 'PREVIOUSLY CALLED TFC, TFC ALERT, 11 O'CLOCK POS, CORRECTION 1 O'CLOCK POS.' I CALLED TFC IN SIGHT, DETERMINED TFC DID NOT POSE AN IMMINENT HAZARD. CTLR CALLED BACK AND STATED THAT I CAUSED A CONFLICT. I ADVISED CTLR TFC NOT A HAZARD, HOWEVER CONFUSION WAS CAUSED BY HER INCORRECT CALL, TWICE, OF THE TFC AT 11 O'CLOCK POS, WHEN IT WAS ACTUALLY AT 1 O'CLOCK POS. CTLR STATED, 'BUT I CORRECTED IT TO 1 O'CLOCK POS.' I ALREADY HAD TFC IN SIGHT AT THAT POINT BECAUSE I LOOKED ELSEWHERE WHEN I DID NOT SEE IT AT POS CALLED. I BELIEVE THIS ERROR OCCURRED DUE TO SPATIAL ORIENTATION CONFUSION ON PART OF CTLR AND CANNOT SUGGEST WAYS TO PREVENT A RECURRENCE, SHORT OF ADDITIONAL TRAINING.
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.