37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Attributes | |
ACN | 1532807 |
Time | |
Date | 201804 |
Local Time Of Day | 1201-1800 |
Place | |
Locale Reference | JBR.Airport |
State Reference | TN |
Environment | |
Flight Conditions | Marginal |
Light | Daylight |
Aircraft 1 | |
Make Model Name | Small Aircraft |
Operating Under FAR Part | Part 135 |
Flight Phase | Final Approach |
Route In Use | Direct |
Flight Plan | IFR |
Aircraft 2 | |
Make Model Name | Any Unknown or Unlisted Aircraft Manufacturer |
Person 1 | |
Function | Captain Pilot Flying |
Qualification | Flight Crew Commercial Flight Crew Instrument Flight Crew Multiengine |
Experience | Flight Crew Last 90 Days 210 Flight Crew Total 1426 Flight Crew Type 1165 |
Events | |
Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Clearance Inflight Event / Encounter Unstabilized Approach |
Miss Distance | Horizontal 0 Vertical 400 |
Narrative:
Inbound to jbr with 1 passenger on board we checked the weather 45 NM out; which was reporting 170 at 4; visibility 10; and 1200 ovc. Due to the ceiling and wind direction we chose to use the ILS approach to runway 23; and informed memphis center that we had the weather/notams and were planning the ILS 23. We were given direct hncok; and began our turn towards the fix. About 10 NM from the fix we were informed to expect to hold over hncok; and it would be the published hold at hncok. We immediately tried to find a published hold for hncok and were not able to do so. At this point we were about 2 NM away from the fix so we decided to clarify with center about the hold. When we asked we were given no information about the hold and immediately told to remain 2;200 feet until established; and we were cleared for the ILS 23 approach into jbr. At this point we began a rapid descent and intercepted the localizer for 23. We began the approach about 800 feet higher than published due to late clearance; but decided to continue the approach because we were able to make a safe and stabilized descent to get back on the glideslope. About 1 NM inside the final approach fix we had not been cleared to change to advisory frequency. We questioned center about this and they immediately told us change to advisory is approved and cancel this frequency or with radio on the ground. We changed over to advisory and made a position report; which was followed by another VFR aircraft in the area. The aircraft made a very similar position report to us; so we decided to check our TCAS for additional situational awareness. We realized that the traffic was directly below us; and decided to go around. We were able to stay clear of clouds at the published traffic pattern and wanted to stay in radio contact with the traffic in the area; so we decided to fly the pattern and land [runway] 23.
Original NASA ASRS Text
Title: Pilot of small fixed wing aircraft reported an NMAC with another aircraft in the vicinity of JBR airport.
Narrative: Inbound to JBR with 1 passenger on board we checked the weather 45 NM out; which was reporting 170 at 4; visibility 10; and 1200 OVC. Due to the ceiling and wind direction we chose to use the ILS approach to runway 23; and informed Memphis Center that we had the weather/NOTAMs and were planning the ILS 23. We were given direct HNCOK; and began our turn towards the fix. About 10 NM from the fix we were informed to expect to hold over HNCOK; and it would be the published hold at HNCOK. We immediately tried to find a published hold for HNCOK and were not able to do so. At this point we were about 2 NM away from the fix so we decided to clarify with Center about the hold. When we asked we were given no information about the hold and immediately told to remain 2;200 feet until established; and we were cleared for the ILS 23 approach into JBR. At this point we began a rapid descent and intercepted the localizer for 23. We began the approach about 800 feet higher than published due to late clearance; but decided to continue the approach because we were able to make a safe and stabilized descent to get back on the glideslope. About 1 NM inside the final approach fix we had not been cleared to change to advisory frequency. We questioned center about this and they immediately told us change to advisory is approved and cancel this frequency or with radio on the ground. We changed over to advisory and made a position report; which was followed by another VFR aircraft in the area. The aircraft made a very similar position report to us; so we decided to check our TCAS for additional situational awareness. We realized that the traffic was directly below us; and decided to go around. We were able to stay clear of clouds at the published traffic pattern and wanted to stay in radio contact with the traffic in the area; so we decided to fly the pattern and land [runway] 23.
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.