Close Call at Boston Logan
FR24 datarecords captured at exactly the same moment (2023-02-27T23:54:57Z):
(JetBlue 206 going around 4R / Hop-A-Jet 280 taking-off rwy 9)
(JetBlue 206 going around 4R / Hop-A-Jet 280 taking-off rwy 9)
Last edited by DIBO; 28th Feb 2023 at 19:08. Reason: added context info
Tough to armchair this incident due to limitations of LiveATC. Available audio feed is both KBOS tower frequencies combined in a single audio file. Not all transmissions are heard. When LC instructs Learjet to cross 4L at E and turn right on M, only a partial read back is heard. When LC instructs Learjet to monitor 132.22, no read back is heard. No read back is heard from LC instruction to Learjet to LUAW on 9, with that transmission excluding the Learjet identifier from LC.
Listening to the extended audio file, radio comms/discipline was very good with both pilots and ATC identifying and correcting occasional errors from the other. Given that exhibited discipline, I suspect the Learjet responded to all LC instructions with the appropriate read back, but not captured on audio file due to limitations of LiveATC monitor. Once off the ground, Learjet comms are loud and clear.
VASAviation creator noted in comments of his video that he followed the Learjet for several frequency changes after departure and never heard ATC issue a possible pilot deviation.
One other observation: after JBU gets handed off from tower, TRACON asks for reason for go-around, and pilot responds "tower instructed" (rather than pilot-initiated).
Listening to the extended audio file, radio comms/discipline was very good with both pilots and ATC identifying and correcting occasional errors from the other. Given that exhibited discipline, I suspect the Learjet responded to all LC instructions with the appropriate read back, but not captured on audio file due to limitations of LiveATC monitor. Once off the ground, Learjet comms are loud and clear.
VASAviation creator noted in comments of his video that he followed the Learjet for several frequency changes after departure and never heard ATC issue a possible pilot deviation.
One other observation: after JBU gets handed off from tower, TRACON asks for reason for go-around, and pilot responds "tower instructed" (rather than pilot-initiated).
Join Date: Dec 2018
Location: Florida
Posts: 193
Likes: 0
Received 0 Likes
on
0 Posts
The area of KBOS where this took place was once emphasized on KBOS charts as a critical hot spot as I recall from years ago, but I am not seeing that on current charts.
https://images.app.goo.gl/c6gb3WzBHsDmSheY8
https://images.app.goo.gl/c6gb3WzBHsDmSheY8
Join Date: Dec 2018
Location: Florida
Posts: 193
Likes: 0
Received 0 Likes
on
0 Posts
Lowest recorded altitude was 75 feet. There are reports that the wheels touched the runway.
https://flightaware.com/live/flight/.../KBOS/tracklog
https://flightaware.com/live/flight/.../KBOS/tracklog
Eyes n' ears open, seems to be a busy season for oddities.
Pegase Driver
Join Date: May 1997
Location: Europe
Age: 73
Posts: 3,425
Likes: 0
Received 0 Likes
on
0 Posts
@ DIBO : could you again put the audio link ? Thanks . This one sounds a bit like Teneriffe,i.e. minset to go before actual take off clearance was issued. We all thought the " lineup and wait " phraseology introduced after that would eliminate this, proved wrong again apparently.
Thread Starter
Join Date: Jan 2019
Location: Up
Posts: 99
Likes: 0
Received 0 Likes
on
0 Posts
@ DIBO : could you again put the audio link ? Thanks . This one sounds a bit like Teneriffe,i.e. minset to go before actual take off clearance was issued. We all thought the " lineup and wait " phraseology introduced after that would eliminate this, proved wrong again apparently.
Assume you’re referring to a possible pilot deviation notification by ATC? While the VASAviation video guy stated he never heard such an ATC notification, another comment in his video stated that HPJ280 was notified about 35 minutes after departure. 7110.65 states that possible pilot deviation notifications are made “workload permitting.” Doesn’t really matter as the FAA has stated via media that HPJ280 departed with no takeoff clearance. I have no doubt that upon arrival at FXE, the pilots were well aware of their regulatory peril.
Join Date: Nov 2004
Location: Here, there, and everywhere
Posts: 1,032
Likes: 0
Received 10 Likes
on
5 Posts
Pegase Driver
Join Date: May 1997
Location: Europe
Age: 73
Posts: 3,425
Likes: 0
Received 0 Likes
on
0 Posts
@Seat4A : Thanks for the audio, Looks like it is partial, the intial call on TWR freq and the readback of the Learjet are missing for instance.
Most probably because the TWR sup wanted to listen to the recording to make sure what was said before making a decision . Quite normal and professional There was no real hurry to do anything right after the. incident .
Most probably because the TWR sup wanted to listen to the recording to make sure what was said before making a decision . Quite normal and professional There was no real hurry to do anything right after the. incident .
Assume you’re referring to a possible pilot deviation notification by ATC? While the VASAviation video guy stated he never heard such an ATC notification, another comment in his video stated that HPJ280 was notified about 35 minutes after departure. 7110.65 states that possible pilot deviation notifications are made “workload permitting.” Doesn’t really matter as the FAA has stated via media that HPJ280 departed with no takeoff clearance. I have no doubt that upon arrival at FXE, the pilots were well aware of their regulatory peril.
Welll...with this recent amount of "Near" & "Close" last times, i really pray one of these next days we won't see such words changing to something worst...
