Private jet tracker · Operator · Air ambulance
Aerocare tracker: fleet & flights live
Over the last 90 days we recorded 3 different jets flying under the callsign SYD. In the last 30 days that added up to 32 flights, most often on Beechcraft King Air 200/250.
ICAO callsign: SYD
Profile
- Legal name
- Flying Ambulance (Pty) Ltd T/A Aerocare
- Country
- South Africa
- ICAO code
- SYD
- Radio callsign
- SKYDOCTOR
- Type
- Air ambulance
- Busiest airport
- Cape Town (FACT)
Legal name, country and radio callsign: FAA ICAO designator list (JO 7340.2). Fleet and flights: ADS-B reception.
- Jets (90 days)
- 3
- Flights (30 days)
- 32
- Airborne now
- 0
- Flight hours (30 d)
- 84.6
- CO₂ (30 d, estimated)
- 74.9 t
Live fleet map
Fleet: tracked jets
3 jets that flew under the operator callsign in the last 90 days, sorted by number of flights.
| # | Registration | Type | Flights 90 d | Last seen |
|---|---|---|---|---|
| 1 | ZS-LRS | Beechcraft King Air 200/250Turboprop | 27 | 11/02/26, 05:57 AM UTC |
| 2 | ZS-PLJ | Beechcraft King Air 200/250Turboprop | 26 | 11/01/26, 12:08 PM UTC |
| 3 | ZS-LFW | Beechcraft King Air 200/250Turboprop | 3 | 10/16/26, 03:04 AM UTC |
Aircraft types in the fleet
Number of tracked jets per type (90 days)
- Beechcraft King Air 200/250BE203 jets
Busiest airports
Departures and arrivals, last 30 days
- 1FACTCape Town8 mov.
- 2FAGCMidrand2 mov.
- 3FAKMKimberley2 mov.
- 4FADADe Aar1 mov.
- 5FAGMJohannesburg1 mov.
- 6FATPBain's Vlei1 mov.
Busiest routes
Flights in the last 90 days
Flight hours & CO₂
Last 30 days
- Flights
- 32
- Flight hours
- 84.6
- Distance
- 17,458 km
- CO₂
- 74.9 t
Year to date
- Flights
- 56
- Flight hours
- 134
- Distance
- 27,268 km
- CO₂
- 119 t
Recent flights
| Date (UTC) | Jet | From | To | Duration | Distance | CO₂ |
|---|---|---|---|---|---|---|
| 11/02/26, 05:40 AMsignal lost | ZS-LRSBE20 | not observed | not observed | 17 min | 130 km | 251 kg |
| 11/01/26, 09:03 PM | ZS-LRSBE20 | FACTCape Town | FAKMKimberleyRoute → | 6 h 59 min | 1,640 km | 6.2 t |
| 11/01/26, 11:46 AMsignal lost | ZS-PLJBE20 | FAGCMidrand | not observed | 22 min | 134 km | 324 kg |
| 11/01/26, 09:43 AM | ZS-LRSBE20 | not observed | FACTCape Town | 9 h 11 min | 1,285 km | 8.1 t |
| 11/01/26, 06:39 AM | ZS-PLJBE20 | FACTCape Town | FAGCMidrandRoute → | 2 h 45 min | 1,320 km | 2.4 t |
| 11/01/26, 02:36 AM | ZS-PLJBE20 | not observed | FACTCape Town | 2 h 14 min | 824 km | 2 t |
| 10/31/26, 03:57 PM | ZS-LRSBE20 | FACTCape Town | not observed | 1 h 56 min | 874 km | 1.7 t |
| 10/31/26, 09:11 AM | ZS-LRSBE20 | not observed | FACTCape Town | 4 h 39 min | 981 km | 4.1 t |
| 10/30/26, 01:15 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 4 h 20 min | 302 km | 3.8 t |
| 10/29/26, 03:13 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 4 h 15 min | 767 km | 3.8 t |
| 10/28/26, 05:11 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 22 min | 171 km | 324 kg |
| 10/28/26, 03:35 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 12 min | 90 km | 177 kg |
| 10/27/26, 08:01 PM | ZS-LRSBE20 | not observed | FATPBain's Vlei | 4 h 28 min | 331 km | 4 t |
| 10/27/26, 08:16 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 49 min | 320 km | 723 kg |
| 10/24/26, 07:51 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 25 min | 212 km | 369 kg |
| 10/24/26, 02:59 PM | ZS-LRSBE20 | not observed | not observed | 1 h 15 min | 457 km | 1.1 t |
| 10/20/26, 06:05 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 4 h 33 min | 690 km | 4 t |
| 10/19/26, 09:08 AMsignal lost | ZS-LRSBE20 | not observed | not observed | 1 h 48 min | 200 km | 1.6 t |
| 10/16/26, 03:54 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 46 min | 349 km | 678 kg |
| 10/16/26, 08:20 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 42 min | 304 km | 619 kg |
| 10/16/26, 02:48 AMsignal lost | ZS-LFWBE20 | not observed | not observed | 16 min | 117 km | 236 kg |
| 10/15/26, 08:38 PM | ZS-LFWBE20 | not observed | FAKMKimberley | 3 h 45 min | 712 km | 3.3 t |
| 10/13/26, 04:06 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 34 min | 265 km | 501 kg |
| 10/13/26, 10:25 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 59 min | 353 km | 870 kg |
| 10/12/26, 08:45 AM | ZS-LRSBE20 | not observed | FAGMJohannesburg | 18 min | 124 km | 265 kg |
| 10/11/26, 05:12 PMsignal lost | ZS-LRSBE20 | FACTCape Town | not observed | 2 h 01 min | 890 km | 1.8 t |
| 10/11/26, 10:39 AM | ZS-LRSBE20 | not observed | FACTCape Town | 4 h 13 min | 974 km | 3.7 t |
| 10/10/26, 03:02 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 4 h 25 min | 482 km | 3.9 t |
| 10/09/26, 01:45 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 19 min | 125 km | 280 kg |
| 10/09/26, 12:31 AM | ZS-PLJBE20 | not observed | FADADe Aar | 30 min | 196 km | 442 kg |
| 10/07/26, 11:54 AMsignal lost | ZS-LRSBE20 | not observed | not observed | 6 h 31 min | 576 km | 5.8 t |
| 10/06/26, 06:56 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 8 h 28 min | 1,263 km | 7.5 t |
| 10/03/26, 12:24 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 3 h 10 min | 425 km | 2.8 t |
| 10/01/26, 01:30 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 4 h 21 min | 587 km | 3.8 t |
| 09/30/26, 09:28 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 3 h 21 min | 605 km | 3 t |
| 09/30/26, 11:11 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 4 h 35 min | 810 km | 4.1 t |
| 09/30/26, 05:29 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 51 min | 388 km | 752 kg |
| 09/29/26, 11:05 PMsignal lost | ZS-PLJBE20 | not observed | not observed | 1 h 14 min | 523 km | 1.1 t |
| 09/29/26, 12:10 AMsignal lost | ZS-PLJBE20 | not observed | not observed | 4 h 18 min | 651 km | 3.8 t |
| 09/28/26, 12:05 PMsignal lost | ZS-LRSBE20 | not observed | not observed | 4 h 38 min | 735 km | 4.1 t |
All times in UTC.
Aerocare FAQ
How many jets does Aerocare have?
Over the last 90 days we recorded 3 different jets under the ICAO callsign SYD, 3 of them also in the last 30 days. The actual fleet may be larger: jets out of receiver range, in maintenance or flying under a different callsign are not counted.
Where is Aerocare based?
According to the ICAO designator list published by the US Federal Aviation Administration (FAA), Flying Ambulance (Pty) Ltd T/A Aerocare is registered in South Africa. The list records the three-letter ICAO code, country and radio callsign of every operator.
What callsign does Aerocare use?
Aerocare flies under the ICAO callsign SYD; on the radio the crew identifies as "SKYDOCTOR". On flight-tracking maps the callsign shows up as the code plus a flight number, e.g. SYD123. That is how we attribute flights to the operator.
Which aircraft types does Aerocare fly?
The types we recorded most often under the Aerocare callsign over the last 90 days: Beechcraft King Air 200/250 (3 jets).
Where does Aerocare fly most often?
Most departures and arrivals in the last 30 days were at Cape Town (FACT, 8 movements), Midrand (FAGC, 2 movements) and Kimberley (FAKM, 2 movements). The busiest route of the last 90 days was Cape Town → Midrand (1 flight).
How much CO₂ does the Aerocare fleet emit?
In the last 30 days the recorded flights emitted an estimated 74.9 t of CO₂ over 84.6 flight hours; year to date it is 119 t from 56 flights. The estimate multiplies the typical fuel burn of the aircraft class by flight time and 3.16 kg of CO₂ per kg of jet fuel.
How can I track Aerocare live?
The map above shows every jet of the fleet that is currently broadcasting ADS-B positions (0 airborne at the last update). Click a registration to open the flight history and live position of that jet. Flights are assigned via the ICAO callsign SYD.
Fly the same jet type as an empty leg
Challenger, Citation or Gulfstream: when jets reposition without passengers, operators often sell the seats at a steep discount.
Data sources & notes
Data source: public ADS-B data
All positions come from publicly broadcast ADS-B signals that every aircraft transmits unencrypted and that volunteers around the world receive. Data may be delayed, incomplete or inaccurate.
Linking an aircraft to a well-known person is based on public sources such as media reports and registry data. "Jet attributed to X" explicitly does not mean that this person is on board or ordered the flight. Aircraft are also chartered, sold or used by others.
All information is provided without warranty; no liability is accepted for accuracy or completeness. CO₂ figures are estimates based on typical fuel burn for the aircraft class.
Using this data to harass, track or stalk people is prohibited.
Are you the owner, operator or an authorised representative and want an aircraft hidden? Submit a removal request
Corrections to [email protected].