 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Near midair collision with near same altitude, crossing traffic. TA given, traffic not sighted as it was in the wrong position as given by the approach controller.
| Attributes | |
| ACN | 345535 |
| Time | |
| Date | 199608 |
| Day | Sun |
| Local Time Of Day | 1201 To 1800 |
| Place | |
| Locale Reference | airport : owd |
| State Reference | MA |
| Altitude | msl bound lower : 3000 msl bound upper : 3100 |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Controlling Facilities | tracon : bos |
| Operator | general aviation : personal |
| Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Flight Plan | IFR |
| Aircraft 2 | |
| Make Model Name | Baron 55/Cochise |
| Operating Under FAR Part | Part 91 |
| Flight Phase | cruise other |
| Flight Plan | VFR |
| Person 1 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Qualification | pilot : instrument pilot : commercial |
| Experience | flight time last 90 days : 24 flight time total : 2549 flight time type : 2046 |
| ASRS Report | 345535 |
| Person 2 | |
| Affiliation | Other |
| Function | flight crew : single pilot |
| Events | |
| Anomaly | conflict : nmac non adherence : far other anomaly other |
| Independent Detector | other flight crewa |
| Resolutory Action | none taken : detected after the fact |
| Consequence | Other |
| Miss Distance | horizontal : 0 vertical : 100 |
| Supplementary | |
| Primary Problem | ATC Human Performance |
| Air Traffic Incident | Pilot Deviation other |
Narrative:
Descended from 9000 ft to 3000 ft to be cleared to 2000 ft. Clearance amended to remain at 3000 ft. Intention to land norwood, ma. Traffic reported at 3100 ft, 12 O'clock, 3 mi. Then 3100 ft, 12 O'clock, 2 mi. Then, 2 O'clock, 1 mi. Passenger and pilot exercised very vigorous scan. No contact. Then traffic spotted 100 ft overhead on crossing course beginning at 5 O'clock crossing to 10 O'clock position. Traffic was a beech baron. We did not receive any instructions to deviate. Baron was headed north, we were headed northeast. Given our scan and the subsequent crossing path it does not seem possible for the baron to have been at our 12 O'clock at any time. We think the controller mixed 6 O'clock position with 12 O'clock position. Question: why weren't we given instructions to deviate?
Original NASA ASRS Text
Title: NMAC WITH NEAR SAME ALT, XING TFC. TA GIVEN, TFC NOT SIGHTED AS IT WAS IN THE WRONG POS AS GIVEN BY THE APCH CTLR.
Narrative: DSNDED FROM 9000 FT TO 3000 FT TO BE CLRED TO 2000 FT. CLRNC AMENDED TO REMAIN AT 3000 FT. INTENTION TO LAND NORWOOD, MA. TFC RPTED AT 3100 FT, 12 O'CLOCK, 3 MI. THEN 3100 FT, 12 O'CLOCK, 2 MI. THEN, 2 O'CLOCK, 1 MI. PAX AND PLT EXERCISED VERY VIGOROUS SCAN. NO CONTACT. THEN TFC SPOTTED 100 FT OVERHEAD ON XING COURSE BEGINNING AT 5 O'CLOCK XING TO 10 O'CLOCK POS. TFC WAS A BEECH BARON. WE DID NOT RECEIVE ANY INSTRUCTIONS TO DEVIATE. BARON WAS HEADED N, WE WERE HEADED NE. GIVEN OUR SCAN AND THE SUBSEQUENT XING PATH IT DOES NOT SEEM POSSIBLE FOR THE BARON TO HAVE BEEN AT OUR 12 O'CLOCK AT ANY TIME. WE THINK THE CTLR MIXED 6 O'CLOCK POS WITH 12 O'CLOCK POS. QUESTION: WHY WEREN'T WE GIVEN INSTRUCTIONS TO DEVIATE?
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.