Dispatcher reported that maintenance operations authorized a non check captain to do a dual engine c...

Narrative:

While planning the in flight functional check; ifc; for a dual engine change; the regional controller received clearance from the fight operations [manager] to use a non-check airman to complete the ifc. This captain was a high minimums captain. Ca (captain) and I had a brief about the flight and about the fact that he would need to taxi over for fuel due to the airport layout. At XA17 ca blocked out after fueling. Approximately XA20 maintenance controller for the flight asked regarding the status of the aircraft as it was still OTS (out of service) and was unaware of a flight on it. After looking into the status and verifying tail number I ACARS'd the aircraft at XA22 stating to not depart without being in mrf status; however wheels up was at XA22. At XA24 an mrf came through from maintenance on my airworthiness management board. Aircraft completed the functional check and landed without incident. Ca called me after the flight to discuss the airworthiness issue and I explained mrfirst officerts/is as well as the fom location for his part of airworthiness management.main causes were a captain who was unaware of the airworthiness management process for ifcs as well as a lack of communication between dispatch/ca on verifying airworthiness prior to departure. Providing a similar OTS message through ACARS that revenue/repo flights do for the flight. Further training on mrf status for ifcs for pilots as the ca specifically stated that he was not trained in regards to this. Potentially a system within the ACARS client for dispatch to be aware of maintenance airworthiness issues after block out.

Original NASA ASRS Text

Title: Dispatcher reported that Maintenance Operations authorized a non check Captain to do a dual engine change In flight Functional Check; who was unsure of requirements for this type of flight.

Narrative: While planning the in flight functional check; IFC; for a dual engine change; the Regional Controller received clearance from the Fight Operations [Manager] to use a non-check airman to complete the IFC. This Captain was a high minimums Captain. CA (Captain) and I had a brief about the flight and about the fact that he would need to taxi over for fuel due to the airport layout. At XA17 CA blocked out after fueling. Approximately XA20 Maintenance Controller for the flight asked regarding the status of the aircraft as it was still OTS (Out of Service) and was unaware of a flight on it. After looking into the status and verifying tail number I ACARS'd the aircraft at XA22 stating to not depart without being in MRF status; however wheels up was at XA22. At XA24 an MRF came through from Maintenance on my airworthiness management board. Aircraft completed the functional check and landed without incident. CA called me after the flight to discuss the airworthiness issue and I explained MRF/OTS/IS as well as the FOM location for his part of airworthiness management.Main causes were a Captain who was unaware of the airworthiness management process for IFCs as well as a lack of communication between Dispatch/CA on verifying airworthiness prior to departure. Providing a similar OTS message through ACARS that revenue/repo flights do for the flight. Further training on MRF status for IFCs for pilots as the CA specifically stated that he was not trained in regards to this. Potentially a system within the ACARS client for Dispatch to be aware of maintenance airworthiness issues after block out.

Data retrieved from NASA's ASRS site and automatically converted to unabbreviated mixed upper/lowercase text. This report is for informational purposes with no guarantee of accuracy. See NASA's ASRS site for official report.

Attributes
ACN	1683731
Time
Date	201909
Local Time Of Day	1201-1800
Place
Locale Reference	TUS.Airport
State Reference	AZ
Environment
Flight Conditions	VMC
Light	Daylight
Aircraft 1
Make Model Name	Medium Transport Low Wing 2 Turbojet Eng
Operating Under FAR Part	Part 121
Flight Phase	Parked
Flight Plan	IFR
Component
Aircraft Component	Turbine Engine
Person 1
Function	Dispatcher
Qualification	Dispatch Dispatcher
Events
Anomaly	Aircraft Equipment Problem Critical Deviation - Procedural FAR Deviation - Procedural Published Material / Policy

Dispatcher reported that maintenance operations authorized a non check captain to do a dual engine change in flight functional check; who was unsure of requirements for this type of flight.