The problem is coming from the property /fdm/jsbsim/damage/repairing.
After a relocation, this property is set to 'true' preventing the aircraft to move (as if the brakes are ON). If the property is set back to 'false', the aircraft is moving again.
I confirm the problem, at least with C172p.
Till today i thought it was relevant to specific RW of some airports. After testing your issue and reading some forum discussion about a Honolulu airport with the same problem, i confirm that the '/fdm/jsbsim/damage/repairing' property remains to 'true' after using 'Location/select Airport' menu option. That removes the ability of aircraft to taxi. I play with 'Aircraft options/Enable damage' and 'Save state of aircraft between sessions' checked.
I noticed that when i toggle the 'Enable damage' option or click on 'repair' button the '/fdm/jsbsim/damage/repairing' property comes to 'true' for some seconds, while repairing lasts i suppose, and then it comes to 'false' again.
It seems problematic that when one sets it to 'true' by hand it does not get back to 'false' after some seconds, as if repairing lasts for ever. It seems problematic also that it happens this property to get a 'true' value, without player noticing it, even when the 'Aircraft options/Enable damage' option is checked. In the last case one expects the property to always be 'false' unless 'repair' button is pressed.
The fact that made me to search for relevant tickets was my today's earlier experience. I started game lined up with active RW but noticed that i was unable to taxi. Obviously, i now understand, that, not only by using the 'Location/select Airport' menu option but, occasionally, the '/fdm/jsbsim/damage/repairing' property can even start as 'true' also.
(I could not reproduce a start of game with 'true' property value in my earlier "debugging" tries today. I use qt launcher and if it uses the same procedures that the 'Location/select Airport' menu option uses, the property should always start as 'true' but it is not the case. In my tries to reproduce the bug at the start of game with qt launcher failed.)
Since i thought that the inability to taxi was relevant to specific airport, i set my aircraft few feet above the RW and took off before my wheels touch the RW below. Since i used the 'Location/select Airport' menu option to get my plane few feet above RW during take off, due to this bug, the 'repairing' property had come to 'true' and i did not know that at the moment. I made a 4 hours flight without noticing any problem but upon landing, since /fdm/jsbsim/damage/repairing' property never got the proper 'false' value during the flight, i experienced a total brake upon touching the RW, unable to taxi and of course without seeing any visible damage on my wheels from external views.
I can not solve the problem, i can only confirm it and thank you for pointing out how to temporary fix it, when one experience the issue in his regular gaming.
Last edit: Jimis Hol 2022-02-03
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I confirm the problem, at least with C172p.
Till today i thought it was relevant to specific RW of some airports. After testing your issue and reading some forum discussion about a Honolulu airport with the same problem, i confirm that the '/fdm/jsbsim/damage/repairing' property remains to 'true' after using 'Location/select Airport' menu option. That removes the ability of aircraft to taxi. I play with 'Aircraft options/Enable damage' and 'Save state of aircraft between sessions' checked.
I noticed that when i toggle the 'Enable damage' option or click on 'repair' button the '/fdm/jsbsim/damage/repairing' property comes to 'true' for some seconds, while repairing lasts i suppose, and then it comes to 'false' again.
It seems problematic that when one sets it to 'true' by hand it does not get back to 'false' after some seconds, as if repairing lasts for ever. It seems problematic also that it happens this property to get a 'true' value, without player noticing it, even when the 'Aircraft options/Enable damage' option is checked. In the last case one expects the property to always be 'false' unless 'repair' button is pressed.
The fact that made me to search for relevant tickets was my today's earlier experience. I started game lined up with active RW but noticed that i was unable to taxi. Obviously, i now understand, that, not only by using the 'Location/select Airport' menu option but, occasionally, the '/fdm/jsbsim/damage/repairing' property can even start as 'true' also.
(I could not reproduce a start of game with 'true' property value in my earlier "debugging" tries today. I use qt launcher and if it uses the same procedures that the 'Location/select Airport' menu option uses, the property should always start as 'true' but it is not the case. In my tries to reproduce the bug at the start of game with qt launcher failed.)
Since i thought that the inability to taxi was relevant to specific airport, i set my aircraft few feet above the RW and took off before my wheels touch the RW below. Since i used the 'Location/select Airport' menu option to get my plane few feet above RW during take off, due to this bug, the 'repairing' property had come to 'true' and i did not know that at the moment. I made a 4 hours flight without noticing any problem but upon landing, since /fdm/jsbsim/damage/repairing' property never got the proper 'false' value during the flight, i experienced a total brake upon touching the RW, unable to taxi and of course without seeing any visible damage on my wheels from external views.
I can not solve the problem, i can only confirm it and thank you for pointing out how to temporary fix it, when one experience the issue in his regular gaming.
Last edit: Jimis Hol 2022-02-03
C172P bugs are tracked at GitHub, where there's an open issue about this problem: https://github.com/c172p-team/c172p/issues/1325