International Marine, Lighthouse Tourism & Maritime Heritage Conference
Dublin Castle 7th & 8th October 2025
What exactly did a lightkeeper do and what was life at a lighthouse really like?
When the last Commissioner’s of Irish Lights lighthouse converted to automatic operation in 2012, the very last lightkeepers were withdrawn from service too. But what exactly did the lightkeeper do and what was life at a lighthouse really like?

Daily Duties
The duty of a lighthouse keeper was primarily to watch the light; or to ‘keep a good light’ as the rules and regulations stated. Back in the days of paraffin-vapour lamps that meant keeping watch in the lantern of the lighthouse, tending the light to make sure it burned as brightly and cleanly as possible, and winding the rotation mechanism to make the light flash correctly, in accordance with its own unique character. A light’s character was the pattern of flashes it displayed, no two lighthouse characters are the same.
Between the 1930s and the 1970s electric lamps were gradually phased in, but these still remained under the keepers’ watch to make sure they operated correctly. Unlike pre-electrification though, watch could be kept in the mess room or kitchen of the lighthouse cottage, where an electric indicator showed that the light was functioning correctly.

At offshore lighthouses and headland lighthouses, the three keepers on duty kept four-hour watches in turn. These watches were from 0200 to 0600, 0600 to 1000, 1000 to 1400, 1400 to 1800, 1800 to 2200, and 2200 to 0200 hours. This meant the same keeper kept the 2am to 6am watch and the 2pm to 6pm watch. However, the watches were changed every Sunday to make sure one keeper wasn’t on the same watch indefinitely.
Fog Watch
During daylight watch the keeper on duty looked out for fog, this was because during fog patches the watches were doubled, with one keeper operating the fog signal while the other tended the light. Each keeper in turn spent the first four hours operating the fog signal and the next four hours tending the light.
During periods of prolonged fog each keeper worked a 16-hour day – and night!
The fog signal could be either an explosive, where the keeper on watch had to detonate an explosive charge at a set interval, or a diaphone signal – a siren activated by compressed air.
At lighthouses with a diaphone fog signal, the keeper had to attend to a large diesel engine which made the compressed air that was then stored in a tank. As the compressed air was continuously being used up by the diaphone, the compressor engine had to run continuously to produce more. The compressor engines were so large it took two men to start them, and when running, they had to be constantly attended to and lubricated to ensure they ran correctly.

House Keeping
In addition to keeping watch and attending to the Aids to Navigation, the keepers carried out routine cleaning, polishing, maintenance work, and general house-keeping duties every day except Sunday. Keeping things shipshape was top priority!
These tasks included cleaning the lighting apparatus, polishing the optic and lantern glass, checking and servicing the engines, painting, keeping the boat-landings and steps free of seaweed, not to mention keeping the living quarters clean.

Keepers would even get calls from fishermen’s wives asking for updates on their husbands’ whereabouts at sea.
While the keepers’ priority was the light and other Aids to Navigation, they also kept an eye on the water and on vessels that passed their way. Keepers would even get calls from fishermen’s wives asking for updates on their husbands’ whereabouts at sea.
Duty Periods
At most offshore lighthouses reliefs were carried out every two weeks, weather permitting. Each keeper in turn was relieved (replaced) by another keeper, so each individual keeper was on duty for six weeks, followed by two weeks off. However, with keepers at the mercy of the weather, when the sea was rough reliefs were often postponed for days or even weeks. When this happened for three reliefs in succession, six weeks duty quickly turned into three or four months or even longer.
When reliefs were overdue and the keeper eventually got ashore, he still had to go back when his two weeks’ liberty was up as the next keeper’s liberty was due, and the cycle would continue.

Keepers were very self-sufficient, each doing his own catering, cooking and washing up. Fresh food was brought to the lighthouse each relief day, but perishable food didn’t last long – tinned and dried foods were heavily relied on. Each keeper kept a large stock of food at the station in case the next relief was delayed.
Each keeper kept a large stock of food at the station in case the next relief was delayed.
They generally had a standing order with a local shop ashore, so each relief day the shopkeeper parcelled up the same items and gave them to the boatman to bring out to the rock. When the keeper came ashore on liberty, he would then settle his account with the local shopkeeper.

Thanks to automation, there’s no longer a need for this harsh and rugged way of life but the love and attention the keepers gave to their lighthouses is still apparent in the heritage, histories and stories that surround the Great Lighthouses of Ireland.
International Marine, Lighthouse Tourism & Maritime Heritage Conference
Dublin Castle 7th & 8th October 2025
| Cookie | Duration | Description |
|---|---|---|
| cookielawinfo-checkbox-advertisement | 1 year | Set by the GDPR Cookie Consent plugin, this cookie is used to record the user consent for the cookies in the "Advertisement" category . |
| cookielawinfo-checkbox-analytics | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics". |
| cookielawinfo-checkbox-functional | 11 months | The cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional". |
| cookielawinfo-checkbox-necessary | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary". |
| cookielawinfo-checkbox-others | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other. |
| cookielawinfo-checkbox-performance | 11 months | This cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance". |
| elementor | never | This cookie is used by the website's WordPress theme. It allows the website owner to implement or change the website's content in real-time. |
| viewed_cookie_policy | 11 months | The cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data. |
| Cookie | Duration | Description |
|---|---|---|
| bcookie | 1 year | LinkedIn sets this cookie from LinkedIn share buttons and ad tags to recognize browser ID. |
| bscookie | 1 year | LinkedIn sets this cookie to store performed actions on the website. |
| li_gc | 5 months 27 days | Linkedin set this cookie for storing visitor's consent regarding using cookies for non-essential purposes. |
| lidc | 1 day | LinkedIn sets the lidc cookie to facilitate data center selection. |
| UserMatchHistory | 1 month | LinkedIn sets this cookie for LinkedIn Ads ID syncing. |
| Cookie | Duration | Description |
|---|---|---|
| _uetsid | never | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
| _uetvid | never | Bing Ads sets this cookie to engage with a user that has previously visited the website. |
| Cookie | Duration | Description |
|---|---|---|
| _ga | 2 years | The _ga cookie, installed by Google Analytics, calculates visitor, session and campaign data and also keeps track of site usage for the site's analytics report. The cookie stores information anonymously and assigns a randomly generated number to recognize unique visitors. |
| _gat_gtag_UA_27868640_1 | 2 hours | Set by Google to distinguish users. |
| _gat_gtag_UA_63181459_1 | 1 minute | Set by Google to distinguish users. |
| _gid | 1 day | Installed by Google Analytics, _gid cookie stores information on how visitors use a website, while also creating an analytics report of the website's performance. Some of the data that are collected include the number of visitors, their source, and the pages they visit anonymously. |
| AnalyticsSyncHistory | 1 month | Linkedin set this cookie to store information about the time a sync took place with the lms_analytics cookie. |
| CONSENT | 2 years | YouTube sets this cookie via embedded youtube-videos and registers anonymous statistical data. |
| iutk | 5 months 27 days | This cookie is used by Issuu analytic system to gather information regarding visitor activity on Issuu products. |
| Cookie | Duration | Description |
|---|---|---|
| IDE | 1 year 24 days | Google DoubleClick IDE cookies are used to store information about how the user uses the website to present them with relevant ads and according to the user profile. |
| MUID | 1 year 24 days | Bing sets this cookie to recognize unique web browsers visiting Microsoft sites. This cookie is used for advertising, site analytics, and other operations. |
| test_cookie | 14 minutes | The test_cookie is set by doubleclick.net and is used to determine if the user's browser supports cookies. |
| VISITOR_INFO1_LIVE | 5 months 27 days | A cookie set by YouTube to measure bandwidth that determines whether the user gets the new or old player interface. |
| YSC | session | YSC cookie is set by Youtube and is used to track the views of embedded videos on Youtube pages. |
| yt-remote-connected-devices | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| yt-remote-device-id | never | YouTube sets this cookie to store the video preferences of the user using embedded YouTube video. |
| Cookie | Duration | Description |
|---|---|---|
| DEVICE_INFO | 5 months 27 days | No description |
| ypsession | 1 month | No description available. |
| ypsitetrack | 1 year | No description |
| yumpu_slc | 7 days | No description available. |