37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1253952 |
Time | |
Date | 201503 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | FPR.Airport |
State Reference | FL |
Environment | |
Flight Conditions | Mixed |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Duke 60 |
Operating Under FAR Part | Part 91 |
Flight Phase | Initial Approach |
Route In Use | Visual Approach Vectors |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Pilot Flying Captain Single Pilot |
Qualification | Flight Crew Multiengine Flight Crew Commercial Flight Crew Instrument |
Experience | Flight Crew Last 90 Days 15 Flight Crew Total 2100 Flight Crew Type 200 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC |
Miss Distance | Horizontal 300 Vertical 200 |
Narrative:
While descending thru broken clouds on vectors for a visual approach to runway 10R at fpr on an IFR flight plan; in contact with miami ATC; ATC instructed to report airport in sight. I advised that we were IMC and was then cleared to lower; 2000 ft if I recall correctly. A few moments later we broke out from the broken layer at approximately 3000 ft MSL and I reported the airport in sight and was instructed to contact fort pierce tower. I switched frequencies and immediately received a TA (traffic advisory system (TAS) equipped). Numerous aircraft were displayed within the 6 mile ring; but we received a yellow TA directly below at 300 ft. I arrested the descent; but the traffic came within 200-300 feet directly below. The frequency was very busy and it took a few moments for me to establish contact with fpr tower. I believe fort pierce tower was in contact with the conflicting aircraft based on one of the tense exchanges taking place. Once I checked in with the tower I was immediately cleared to land on runway 10R and landed without any further drama.upon establishing contact with fort pierce ground control and receiving taxi instructions I made a comment to the ground controller about a concern of a near miss. I was given a phone number for miami ATC. My concern primarily was that while on vectors with miami ATC I was not given any traffic advisories prior to the onboard TAS TA. It seemed I was vectored into the conflict.
Original NASA ASRS Text
Title: BE60 pilot experiences a NMAC after descending through a broken layer under ZMA control. The traffic is not reported by ZMA nor sighted by the reporter but is detected by the onboard Traffic Advisory System.
Narrative: While descending thru broken clouds on vectors for a visual approach to RWY 10R at FPR on an IFR flight plan; in contact with Miami ATC; ATC instructed to report airport in sight. I advised that we were IMC and was then cleared to lower; 2000 FT if I recall correctly. A few moments later we broke out from the broken layer at approximately 3000 FT MSL and I reported the airport in sight and was instructed to contact Fort Pierce tower. I switched frequencies and immediately received a TA (Traffic Advisory System (TAS) equipped). Numerous aircraft were displayed within the 6 mile ring; but we received a yellow TA directly below at 300 FT. I arrested the descent; but the traffic came within 200-300 feet directly below. The frequency was very busy and it took a few moments for me to establish contact with FPR tower. I believe Fort Pierce Tower was in contact with the conflicting aircraft based on one of the tense exchanges taking place. Once I checked in with the tower I was immediately cleared to land on RWY 10R and landed without any further drama.Upon establishing contact with Fort Pierce Ground control and receiving taxi instructions I made a comment to the Ground controller about a concern of a near miss. I was given a phone number for Miami ATC. My concern primarily was that while on Vectors with Miami ATC I was not given any traffic advisories prior to the onboard TAS TA. It seemed I was vectored into the conflict.
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.