Date: 202006
Location: ZZZ.Airport, US
Aircraft: Commercial Fixed Wing
Operator: Air Carrier
Reporter organization: Air Carrier
Reporter function: Dispatcher
Reporter qualification: Dispatch Dispatcher
Human factors: Workload; Distraction; Confusion; Situational Awareness
Second reporter function: Dispatcher
Anomaly: Aircraft Equipment Problem Less Severe; Deviation / Discrepancy - Procedural FAR; Deviation / Discrepancy - Procedural MEL / CDL; Deviation / Discrepancy - Procedural Published Material / Policy
Detector: Person Other Person
Result: General Maintenance Action
Contributing factors: Company Policy; Aircraft; Procedure
Primary problem: Company Policy

Narrative: I received an email from my relief [name omitted] that MEL XYYYZ was added to Aircraft X. I was not aware of this MEL was added to the leg ZZZ/ZZZ1 or subsequent legs and do not recall a call for it's deferral however it was a cluster for the first hour of my shift!Upon signing into position;  I called Mids Dispatcher to get a brief for my AM shift and had 3 leg charter to flight follow also a 2 leg with only 1 release that needed to be sent.  Originally I signed to work [position 1] however was advised that [another positions] desk was the only one that works for [position 1] flights so I proceeded to sign out of [other position] and re-sign into [position 1]. Upon signing in; I had problems with all my applications including my email; applications not working; system kicking offline; and phone issues. (ringing but no one on other line). I had an  IT Rep at my desk for at least an hour to help me spool up the desk.I flight followed [three flights] to their station and did receive a call from Crew of [flight] ZZZ1-ZZZ2 to possibly leave early. (which I set up with FBO in ZZZ2 and advised manager). I do not recall  MEL XYYYZ was added for aircraft. I did again have system kick offline a few times throughout my shift and the manager even walked over to my desk to ask if I was having issues with the system.I found out (from my afternoon relief) that Captain called and was conferenced with Maintenance Control. They found that MEL XYYYZ had been automatically added to the maintenance release after aircraft landed in ZZZ1. (due to the aircraft coming out of storage and limited to Autoland limit land II) The Captain said he overlooked the carry forward items and missed that this MEL was added. I myself did not re-release the subsequent flights and both flights took off without the correct MELs XYYYZ on release. (had I received a call from Maintenance Control; I could have verbally added MEL to release; added a note; brief my relief upon shift change and/or amend the releases). This is an unusual situation because we typically do not bring planes out of storage and MELS are not usually automatically applied after a landing.


Second narrative: This is a series of charter flights starting with:Flight ZZZ ZZZ1Flight ZZZ1 ZZZ2Flight ZZZ3 ZZZShortly after signing in; Flight ZZZ3-ZZZ blocks out of and I get an alert stating 'no new release since MEL change. I investigated the MELs and found that MEL XYYYZ was added after release 1. I tried to stop the crew but could not reach them in time before takeoff. After takeoff I re-released the flight and informed the crew.After landing the Captain called me; we conferenced with Maintenance Control and found that MEL XYYYZ had been automatically added to the maintenance release after Flight X landed in ZZZ1 due to the aircraft coming out of storage and limited to Autoland limit land II. The Captain said he overlooked the carry forward items and missed that this MEL was added. The Dispatcher did not re-release the subsequent flights Y or Z and both flights took off without the correct MELs on release.


Synopsis: Dispatchers reported problems with taking an aircraft out of storage and an associated MEL that was not applied before takeoff.