I was on Fulgora when removing the beacon. Trying to place a beacon over an existing one also shows Unknown key: "entity-name.TP_marker".
I checked the installed PersonalTeleporter 0.5.3 source. At control.lua:682, updateTelporterList() calls:
game.surfaces[teleportSurface].find_entities(...)
This function scans ALL entries in storage.TelaportLocations, not just the beacon being removed. It uses the saved surface name in telaportLoc[4] (or "nauvis" if absent), without checking that the surface still exists. The nil indexing error at this line indicates that game.surfaces[teleportSurface] is nil for one saved destination. So removing a beacon on Fulgora can crash because of a stale entry for another surface. The missing surface and what deleted/renamed it are not yet identified; this does not establish that Cerys caused it.
Suggested fix: guard the surface lookup and clean up stale destinations. Iterate backwards when removing entries with table.remove, and validate the stored marker before calling its destroy() method in removeTelFromList() at line 702. Also handle surface deletion/renaming to keep destinations consistent.
The TP_marker warning is a separate localization issue. prototypes/teleporter-tiers.lua defines TP_marker as the helper train-stop created for each beacon, but locale/en/default.cfg has no TP_marker entry under [entity-name]. Adding it would fix the unknown-key text, but would not fix the line 682 crash.
I have not yet tested removal of other beacons/on other planets, or teleporting to the affected beacon, so those results are still unconfirmed. This analysis is based on source inspection and the stack trace; the proposed fix has not been tested in-game.