| ARRIVED 2 HOUR 55 MINUTES AGO |
 |  |
Departure (BG363 Flight Schedule)
Dhaka, Bangladesh+06 00:00:00 DAY
Arrival (BG363 Flight Schedule)
Madras, IndiaIST 00:00:00 DAY
Flight Radar Checker BG 363
Live Flight Tracker Map
Flight BG363 from Dhaka to Madras is operated by Biman Bangladesh Airlines. Scheduled time of departure from Zia Intl is 11:10 +06 and scheduled time of arrival in Chennai Intl is 13:05 IST. The duration of the flight is 2 hours 55 minutes.
History Flight Information for BG363 from Flight Scanner System
| Date | Flight | Departure Airport | Arrival Airport | Scheduled | Plane | Estimated | ||
|---|---|---|---|---|---|---|---|---|
| Departure | Arrival | Departure | Arrival | |||||
| Wed, 05 Feb | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | S2-AHO (Boeing B738) | 11:20 +06 | 10:48 IST |
| Sat, 01 Feb | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | 11:19 +06 | 11:07 IST | |
| Wed, 29 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | S2-AHV (Boeing B738) | 12:00 +06 | 11:33 IST |
| Sat, 25 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | S2-AHO (Boeing B738) | 11:54 +06 | 11:33 IST |
| Wed, 22 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | 11:12 +06 | 11:31 IST | |
| Sat, 18 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | |||
| Wed, 15 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | 11:22 +06 | 11:12 IST | |
| Sat, 11 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 16:30 +06 | 18:25 IST | S2-AHO (Boeing B738) | 16:44 +06 | 17:57 IST |
| Sat, 04 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 11:10 +06 | 13:05 IST | 11:23 +06 | 10:59 IST | |
| Wed, 01 Jan | BG363 | Zia Intl (DAC) | Chennai Intl (MAA) | 12:55 +06 | 14:50 IST | |||
Disclaimer for BG363 Flight Radar Data
Flight BG363 from Zia Intl to Chennai Intl data is collected from different sources. The data is for informational purposes only and PlaneMapper is not responsible for the accuracy and reliability of flight BG363 data.
