malc-c
Member
- Joined
- 1 Dec 2017
- Messages
- 995
For me, I would stick to the main format of a single podcast, but detail the signalling or track detection practices used in the day at the beginning part of the main podcast. In the last episode the subject matter jumped about a bit, somewhat spoiling the image that was forming in my mind.
Following the introduction to the event, then would be a good time to describe how the block sectioning, signalling and its operation, or any other practices worked, setting the scene for the main event with the description of the trains movements, impact, which was in excellent detail and there was little difference between pictures of the event and how it was described in the pod cast, and resulting aftermath. Then detail the rescue efforts, investigation, conclusions and any impact it had on change to practices or procedures to make sure things become safer. If this increased duration of the episode by 15 minutes I personally would prefer that rather than having to listen to a short 10 minute cast on AWS workings prior to the main episode.
Following the introduction to the event, then would be a good time to describe how the block sectioning, signalling and its operation, or any other practices worked, setting the scene for the main event with the description of the trains movements, impact, which was in excellent detail and there was little difference between pictures of the event and how it was described in the pod cast, and resulting aftermath. Then detail the rescue efforts, investigation, conclusions and any impact it had on change to practices or procedures to make sure things become safer. If this increased duration of the episode by 15 minutes I personally would prefer that rather than having to listen to a short 10 minute cast on AWS workings prior to the main episode.