Narrative:

Pre-flight control check seemed normal. Upon rotation noticed excessive force required to rotate. During initial climb-out confirmed pitch force was much higher than normal. Suspected pitch feel system malfunction but no corresponding cas message was displayed. Leveled off at intermediate altitude and requested course deviation from departure control to remain close to shoreline. Ran abnormal procedures checklist which directed stabilized landing as soon as possible. Contacted chief pilot using iphone [calling] application. Indicated intention to continue on current heading to diversion airport as its heading and distance would allow for a stabilized descent with no turns necessary to align with landing runway. Chief pilot agreed; transferred call to dispatch for a re-release to diversion airport. Call was on hold for five minutes; then call dropped. Attempted to re-establish call but the application would not function properly and was unable to place call. Due to proximity to diversion airport discontinued attempts to contact dispatch for re-release and accomplished uneventful landing. While no action would prevent this type of random mechanical failure; the reliability of the [calling] application could be improved. During the period the [calling] application was unable to make a call; other electronic cockpit devices were able to connect to the aircraft's wi-fi system and access the internet. With [calling application] being the only available option for cockpit to ground telephone communications; its reliability is of great importance.

Google
 

Original NASA ASRS Text

Title: CE750 Captain experiences stiff elevator controls during rotation and in flight. Communication with the company is difficult using an iPhone and the aircraft Wi-Fi system during the diversion to a suitable airport.

Narrative: Pre-flight control check seemed normal. Upon rotation noticed excessive force required to rotate. During initial climb-out confirmed pitch force was much higher than normal. Suspected pitch feel system malfunction but no corresponding CAS message was displayed. Leveled off at intermediate altitude and requested course deviation from Departure Control to remain close to shoreline. Ran abnormal procedures checklist which directed stabilized landing as soon as possible. Contacted Chief Pilot using iPhone [calling] application. Indicated intention to continue on current heading to diversion airport as its heading and distance would allow for a stabilized descent with no turns necessary to align with landing runway. Chief Pilot agreed; transferred call to Dispatch for a re-release to diversion airport. Call was on hold for five minutes; then call dropped. Attempted to re-establish call but the application would not function properly and was unable to place call. Due to proximity to diversion airport discontinued attempts to contact Dispatch for re-release and accomplished uneventful landing. While no action would prevent this type of random mechanical failure; the reliability of the [calling] application could be improved. During the period the [calling] application was unable to make a call; other electronic cockpit devices were able to connect to the aircraft's Wi-Fi system and access the internet. With [calling application] being the only available option for cockpit to ground telephone communications; its reliability is of great importance.

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.