Originally Posted by
upfront777
This thread is very informative Thank you. Reawakening it:
Tuesday I flew BOS to CLT (AA 1453) at close to the peak of the big storm that day- at FL 50' we did a go around (Altitude and big bumps confirmed by the Capt while disembarking). The rest of the story was successful on approach #2 but not without a rodeo. My skills havent been ood enough to find the recording of our flight on Live ATC-- Wondering if someone here might lend some tips? Would be informative to hear the sequence of the crew doing what they train to do. No BigJet TV in CLT but there should have been that day!!
Thanks!
Friendly reminder for those who try to use aviation terminology to sound cool. Make sure you get it right. FL 50 is (can be) an actual thing. And flying BOS-CLT you certainly did not initiate a go around at FL 50. In fact, you were never at FL 50 at all. You see,
in the USA, there is no such thing as FL 50.
Mind those transition levels/transition altitudes!
With that mini-rant out of the way, look up your BOS-CLT flight on flightaware and find its filed flight plans. Were you on AA1453/09? If so, you filed the CHSLY STAR into CLT:
https://www.flightaware.com/live/fli...410Z/KBOS/KCLT
Go to airnav.com or the FAA's own site, pull the plate for that particular arrival and see that arrivals on the CHSLY STAR will usually initially contact approach on 126.15:
https://aeronav.faa.gov/d-tpp/2313/00078CHSLY.PDF
From there, see if 126.15 is a covered frequency on liveatc.net and its archives. Appears that it is not. All may not be lost though as other CLT approach frequencies are covered by liveatc.net:
https://www.liveatc.net/search/?icao=KCLT
Maybe one of those was working final on the day of your flight. Work backwards from the time you touched down and see.
Generally at large airports like CLT you will be talking to
at least two different Approach Control sectors - the initial/feeder controller (126.15) and a final approach controller. Were you at 5000' when you went around you probably were on the final controller's sector.
(Edited to add: Flightaware track log for AA1453/09 shows that the go around was not initiated at 5000'. You hit 1075' on the approach that resulted in a go around. Thus, the go around would certainly have been on the Tower frequency, not approach. Once you've gone around, the handoff from Tower will likely be to a TRACON controller working one of the departures sectors)