 |
37000 Feet | Browse and search NASA's Aviation Safety Reporting System |
|
Small aircraft pilot reported a near midair collision north of lal while on an IFR flight.
| Attributes | |
| ACN | 1439338 |
| Time | |
| Date | 201704 |
| Local Time Of Day | 0601-1200 |
| Place | |
| Locale Reference | ZJX.ARTCC |
| State Reference | FL |
| Environment | |
| Flight Conditions | VMC |
| Light | Daylight |
| Aircraft 1 | |
| Make Model Name | Small Aircraft |
| Operating Under FAR Part | Part 91 |
| Flight Phase | Cruise |
| Route In Use | Direct |
| Flight Plan | IFR |
| Person 1 | |
| Function | Pilot Flying Single Pilot |
| Qualification | Flight Crew Instrument Flight Crew Private |
| Experience | Flight Crew Last 90 Days 40 Flight Crew Total 450 Flight Crew Type 80 |
| Events | |
| Anomaly | ATC Issue All Types Conflict NMAC Deviation - Procedural Published Material / Policy |
| Miss Distance | Vertical 400 |
Narrative:
Flying level at 8000 feet and talking to jacksonville controller; I noticed a plane on ads-B straight ahead and about 7 miles and 1000 feet below. The plane was climbing and when I noticed it at 5 miles and 800 feet; I queried the controller. His response was that I should be on a different frequency and gave me that frequency. On changing frequency; I switched off autopilot and prepared for an immediate turn all while searching for the traffic. On listening to the new frequency; it was clear that the controller was communicating with that plane and was frustrated that I was not in communication with him. Ads-B shows that we were within 400 feet of each other but I never saw the other traffic. The new controller asked what my previous frequency was. The flight proceeded normally thereafter.the problem likely arose from task saturation in the controller's sector due to increased traffic from [an aviation event]. We were just north of lakeland; just west of the center city VOR. A contributing factor is the difficulty in determining the correct communication frequency and change over points for sectors. These are shown; but minimally; on the IFR low charts. In the future; I plan to be much more diligent about which sector I am in and knowing when that sector changes.
Original NASA ASRS Text
Title: Small aircraft pilot reported a NMAC north of LAL while on an IFR flight.
Narrative: Flying level at 8000 feet and talking to Jacksonville controller; I noticed a plane on ADS-B straight ahead and about 7 miles and 1000 feet below. The plane was climbing and when I noticed it at 5 miles and 800 feet; I queried the controller. His response was that I should be on a different frequency and gave me that frequency. On changing frequency; I switched off autopilot and prepared for an immediate turn all while searching for the traffic. On listening to the new frequency; it was clear that the controller was communicating with that plane and was frustrated that I was not in communication with him. ADS-B shows that we were within 400 feet of each other but I never saw the other traffic. The new controller asked what my previous frequency was. The flight proceeded normally thereafter.The problem likely arose from task saturation in the controller's sector due to increased traffic from [an aviation event]. We were just north of Lakeland; just west of the Center City VOR. A contributing factor is the difficulty in determining the correct communication frequency and change over points for sectors. These are shown; but minimally; on the IFR low charts. In the future; I plan to be much more diligent about which sector I am in and knowing when that sector changes.
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.