FSS 2024 Debrief

Krister Larsen (1340812)

In order to improve the experience and get an overview of what worked out, we would be very happy to get feedback from all of you about the event. It can be anything, we are happy to know all aspects.

Daniel Lange (1352906)

ENGM APP the first 2h was quite calm and alright. Nothing big to report.

ENBD CTR the next 1.5h was getting slowly more busy, but with good speed control from ENBD C it was mostly quite a breeze. I did a little whoopsy here by hiding all other CJI's, so I didn't see that ENTC APP was getting overloaded towards the end and APP didn't say anything either. I started holding when another sector gave me a heads up that I should perhaps start holdings.

ENOS N at the last 2 hours was quite straight forward, but enough to do.

Overall, I'd say this was a great event with a decent amount of traffic without totally overloading.

Marius Linge (1621930)

Started out on ENGM TWR, which was rather calm. Spent my break on ENVA APP where we got a good amount of traffic departing northbound.

One concern that appeared was some wrong routing from non-event airports. This could probably be a bit more clear in our briefing. The middle and last part of the event i was a noob NISSE, but this worked out pretty well overall. Would have tried to solve more of the wrong routings if time allowed for it. The FSS MAP was great for catching these!

Some shuffling of people that took some time. The staffing sheet was quite cumbersome to work with, so would be interesting to look at the other solution available for staffing to hopefully make this easier.

Updating the slots via VATCAN was OK. Ideally another option which doesn't require uploading the file would be nice, for examply by having a multiline text field on the page for adding and submitting new lines.

Traffic inbound ENTC seemed to become a bit congested with several holdings later on. Was a bit hard to predict this. Should be have enforced release, or put in place some ECFMP flows? (Did not get access to this before the event, and still don't have it tho.)

Coordination with Sweden worked out very well.

Would be really cool to have some streaming on Twitch/YouTube from Polaris as well.

Overall a great and fun event though. 10/10, would NISSE again.

Krister Larsen (1340812)

ENBD_S_CTR
Nothing special to mention here. Manageable amount of traffic here in this sector.

ENEV_APP
I was originally on STBY and ended up here as there was a groupflight bound for ENEV. Nothing much to comment at, other than it was useful for ENBD_CTR, as the groupflight is unfortunately requiring more attention than normal.

ENTC_APP
It was a new kind of challenge. In summary, everything went okay. There were some hiccups here and there, but with a max arrival rate, I would say I'm satisfied. For next year, I would recommend a better specification around spacing in arriving traffic from ENBD to TC APP

SUP/Planning etc.
Good with all management done by UK. Was some misunderstanding with the spreadsheet. From NISSE it was questioned a more smoother way to add the non-release traffic into ES. Should we be looking into other options than VACAN booking plugin? Was the traffic too calm? Was there high percentage of no-show? This is something that needs to be looked at.
Unfortunately, it was many last-minute changes due to changed availbility at the day of the event and during the event. This is a demanding event and it takes much time to make staffing espesially to this event. With theese changes it's on top of making the staffing makes it more tricky. Although, with good help of Nisse and Event Assistant, we are able to sort out all cases.

Henrik Sonstebo (1203470)

Overall Staffing
Fantastic work on ensuring strong staffing throughout the event! The effort put into covering Norwegian airspace was evident, and it contributed greatly to the event's overall success. Big kudos to everyone involved!

ENBD_CTR
While staffing was solid, I believe ENBD_CTR was split too early, especially into a three-way split. A two-way split would have been more than adequate at the start, keeping the workload manageable while allowing resources to be allocated elsewhere where they were needed more urgently.

ENSV_CTR
Anticipating traffic flows is always challenging, particularly when departures can originate from virtually anywhere at any time. However, given that EGPX_CTR was offline, splitting ENSV_CTR earlier on should have been prioritized. The lack of coverage in Scottish airspace directly impacted our ability to manage traffic effectively, as I had to focus on resolving conflicts 50 nmi before my airspace.

EGPX_CTR
EGPX_CTR really needed to be online for this event. On multiple occasions, I received aircraft from Scottish airspace that were either poorly separated or had attempted self-separation, creating further complications for us down the line. This added unnecessary complexity to an already busy event and impacted flow efficiency.