A word of advice => don't do this.
In general Jeffery's answer provides a recipe for initializing static resources, however it may not be a good idea to apply it to loading a JavaFX Image.
Due to RT-30796 Cannot create a JavaFX Image until "Internal graphics" are initialized, it is not advised to attempt to create a JavaFX Image in a static context.
The issue in RT-30796 which prevents loading of a JavaFX Image in a static context before the JavaFX internal graphics engine is initialized may or may not be addressed in a future version of JavaFX. (A sign up is required to view the issue tracker, but anybody can sign up to view it).
Instead, I recommend modifying your application logic to create your image in a non-static context, once you are sure that the JavaFX toolkit has been appropriately initialized for your application (for example once your application's init or start methods have been invoked or your JFXPanel created).
Additionally, for loading a JavaFX image, I do not recommend using ImageIO. ImageIO creates AWT images which you then need to convert to JavaFX images. Using the JavaFX Image constructor is a more direct route and will work on compact Java profiles on embedded platforms where AWT and ImageIO may not be available.