Aircraft

G-FBEF

Commonnot seen for 6 years

Identity resolved on 13 Aug 2026: the aircraft was too recent for the registry at the time of the first contact, on 11 Apr 2016. What this page shows comes from a later registry; each contact keeps what was known on the day it was heard.

Notify me at the next passage

Mode S hex: 401229
Type: Embraer 190E190
Manufacturer: Empresa Brasileira De Aeronautica Sa
Serial number: 19000104
Year built: 200719 years old
Operator: Flybe (BEE)
Country of registration: Royaume-UniICAO address allocated by United Kingdom, aircraft registered in Royaume-Uni.
First contact: 11 Apr 2016, 14:07
Last contact: 31 Aug 2019, 20:10
Logged visits: 522

G-FBEF — Photo © Josh Knights · planespotters.net

The station's story

Address not received since 31 Aug 2019. The marker states the absence, it does not say why.

Cumulative contact time: 195 h
Distinct days: 263
Highest captured altitude: 41,000 ft; 1 corrupted frame(s) excluded from this maximum
Discovery rank: #5,269 of 57,252
Longest contact: 1 h 3 min

Observed callsigns

BEE (342 contacts, 2016-2019) · STK (134 contacts, 2017-2018)

Operator as per the registry of 12 Aug 2026; observed callsigns are the freshest measurement.

Visits

Callsign	Route	First contact	Last contact	Altitude at end of contact	Positions
not transmitted	route not resolved	24 Dec 2018, 16:3524 Dec 2018	24 Dec 2018, 16:38	not transmitted	no position received	›
BEE128M	route not resolved	23 Dec 2018, 12:3923 Dec 2018	23 Dec 2018, 12:58	36,000 ft	no position received	›
BEE867N	route not resolved	23 Dec 2018, 10:4823 Dec 2018	23 Dec 2018, 11:07	5,925 ft	no position received	›
BEE1EL	? > EGBB	22 Dec 2018, 15:5422 Dec 2018	22 Dec 2018, 16:16	34,000 ft	no position received	›
BEE635G	route not resolved	22 Dec 2018, 13:3522 Dec 2018	22 Dec 2018, 13:50	37,000 ft	no position received	›
BEE417B	route not resolved	21 Dec 2018, 15:2521 Dec 2018	21 Dec 2018, 15:34	38,000 ft	no position received	›
not transmitted	route not resolved	21 Dec 2018, 13:2821 Dec 2018	21 Dec 2018, 13:28	37,000 ft	no position received	›
STK6101	route not resolved	9 Nov 2018, 17:209 Nov 2018	9 Nov 2018, 17:35	32,000 ft	no position received	›
STK6101	route not resolved	31 Oct 2018, 16:3931 Oct 2018	31 Oct 2018, 16:54	34,550 ft	no position received	›
not transmitted	route not resolved	29 Oct 2018, 19:0129 Oct 2018	29 Oct 2018, 19:01	not transmitted	no position received	›
STK38D	route not resolved	26 Oct 2018, 20:3926 Oct 2018	26 Oct 2018, 20:52	36,000 ft	no position received	›
STK69P	route not resolved	26 Oct 2018, 18:0426 Oct 2018	26 Oct 2018, 18:23	26,175 ft	no position received	›
STK32W	route not resolved	26 Oct 2018, 15:0326 Oct 2018	26 Oct 2018, 15:20	36,000 ft	no position received	›
STK38D	route not resolved	25 Oct 2018, 20:2425 Oct 2018	25 Oct 2018, 20:48	36,000 ft	no position received	›
STK69P	route not resolved	25 Oct 2018, 18:0125 Oct 2018	25 Oct 2018, 18:27	29,000 ft	no position received	›
STK32W	route not resolved	25 Oct 2018, 15:1025 Oct 2018	25 Oct 2018, 15:23	34,275 ft	no position received	›
STK38D	route not resolved	22 Oct 2018, 20:3422 Oct 2018	22 Oct 2018, 20:53	38,000 ft	no position received	›
STK69P	route not resolved	22 Oct 2018, 18:4422 Oct 2018	22 Oct 2018, 19:08	25,025 ft	no position received	›
STK32W	route not resolved	22 Oct 2018, 15:5622 Oct 2018	22 Oct 2018, 16:09	34,850 ft	no position received	›
STK32W	route not resolved	21 Oct 2018, 12:4921 Oct 2018	21 Oct 2018, 13:02	35,125 ft	no position received	›
STK32W	route not resolved	20 Oct 2018, 18:3420 Oct 2018	20 Oct 2018, 18:50	36,000 ft	no position received	›
STK32W	route not resolved	18 Oct 2018, 14:5218 Oct 2018	18 Oct 2018, 15:06	38,000 ft	no position received	›
STK32W	route not resolved	17 Oct 2018, 14:3717 Oct 2018	17 Oct 2018, 14:51	34,000 ft	no position received	›
STK32W	route not resolved	8 Oct 2018, 14:598 Oct 2018	8 Oct 2018, 15:10	29,150 ft	no position received	›
STK38D	route not resolved	7 Oct 2018, 20:277 Oct 2018	7 Oct 2018, 20:44	30,000 ft	no position received	›