Before going into warp, your ship has to align itself perfectly with the direction you're headed in. This has been known to backfire when your ship is either close to some celestial object or is facing the opposite direction from your destination (though it's not completely restricted to these circumstances), which multiplies the amount of fine tuning required for the impending warp and effectively leaves you defenseless. The best way to avoid this is to ensure that you don't go into warp when you're right next to objects in space or are facing the wrong direction. You can use the ship's manual navigation controls to fly away from those objects and turn as needed before going into warp. Having an afterburner or a microwarpdrive fitted can sometimes help under these circumstances and the ship's agility is also a big factor when aligning for warp.

NOTE: You can cancel warp by right clicking on your ship and giving the ´stop my ship´ command. It will break the warp and you´ll be in charge of the ship again. You can also hit the "control" and "spacebar" keys on your keyboard simultaneously to stop the warping process. This only applies though when the ship is still aligning itself and getting ready to warp. If the autopilot is engaged, you'll have to turn it off to prevent your ship from going straight back into warp mode.

Not reimbursed

As for reimbursement, we're sorry but it's extremely unlikely. We use our own logs for verification when evaluating requests, and we simply do not have the data on such detailed ship actions as going into - and being stuck in - warp. The only thing we see is that someone's ship was destroyed by another party. We don't doubt your word, but if we were to reimburse people who claimed to have lost their ships when being stuck in warp we would be completely inundated with requests from everyone else every time they lost a battle with an NPC pirate or another player.
Incidentally, we very strongly suggest that you always have your ship insured. It won't bring everything back, but will at least mitigate the loss.

Still file a bug report

If you are able to replicate this, though, you can assist CCP in streamlining the warp procedure and decreasing the time required. This will not make you a candidate for reimbursement, but it will help increase your future safety. What follows are instructions on three files that CCP would need. Please file this information through a bug report.

Note that bug reports are not seen by Customer Support, but you should receive a status update from our testing teams.

First, a DxDiagnostics file. Open C:\Program Files\directx\setup and double click on the DxDiag icon. When you do this, a window will pop up. Click the "Save All Information" button that's located in its lower right corner. You can also start the tool by going to Start -> Run, typing dxdiag and pressing Enter.
(Most of this information can also be found by pressing Start -> Settings -> Control Panel, double-clicking on the "System" icon and browsing through the hardware profiles. Note that we do need all information about driver versions.)

Second, a LogServer file. If you can reproduce the circumstances then this is *vital*. Should this case come under review from the developers at CCP then they won't get far without this file.
(Note that if you're unwilling to spend money and equipment doing this on the normal playing server, which is perfectly normal, you can do it on the internal test server where you won't lose any permanent progress - more information can be found on http://www.eve-online.com/patches/patches.asp?s=singularity)
Look for the- logserver.exe in your EVE directory. Each time you want to make a useful log, do the following:

• Locate LogServer.exe under the EVE folder (c:\program files\ccp\eve\)
• Start LogServer.exe
• In LogServer Click on "new workspace"
• Start EVE.exe

Now when you look at he log server while running EVE you should be able to see that the log server is logging events. In cases when you want to send the log with either a bug report or when contacting customer support, simply select "File->Save Workspace As" in the LogServer and name the file [yourcharactername]Log.

Aside from these, screenshots of the warp slowdown in progress will help but only if you convert them to .jpg format. Other file types will be too large for our system to accept. You can take the screenshots by pressing Print Screen and then pasting the outcome into a graphics program. Also, if you have and use WinZip, putting all the files into an archive will help immensely.

Attach these files or the archive to the bug report and hopefully CCP will be able to use them to rid us of this extended wait.