Expedition 2006 - South Africa and Lake Malawi

JBL Expedition 2006 - South Africa and Lake Malawi

JBL Expedition 2006 - South Africa and Lake Malawi

Sand tiger sharks

The team was primarily interested in the coral reef off the coast. The reef runs at a depth of 15 to 40 meters parallel to the coast south of Durban. The diving sites were reached after about 15 – 20 minutes by boat. With the high waves, the trip is not for anyone with a delicate stomach! Although the plan was to feed the fish with JBL MariPearls, many of the team members involuntarily fed the fish on the trip out there!

With water temperatures of 22 to 24 °C, thicker wet suits were definitely called for! The water was relatively cloudy and visibility was restricted to about 10 to 15 m. The coral reef is very impressive in places. Hard and soft corals, sponges and other invertebrates cover the ancient reef stone. The coral communities cannot be compared with “normal“ tropical reefs. Amongst the fish, many species can be seen which are typical for regions close to the Antarctic. The mixture of tropical and coldwater species is astounding!

The shark course with Andy Cobb had prepared the team for their encounters with sand tiger sharks. The shark usually remain in one area and are not very shy at all. However, if divers become impatient and get too close to the creatures, they will sometimes flee to deeper waters for several days.

The Swiss team member, Michel Comte, carried out underwater feeding trials with JBL MariPearls. The strong current made this experiment highly complicated. Nevertheless, many species of fish could be observed feeding. As in previous trials, it was noted that chaetodon species (butterfly fish) were not interested in the food. Just for fun, food granulate was sprinkled on the surface of the water. The skipper observed from the boat that the mantas noticed the food immediately (they were over 3 m long!) and eagerly filtered it from the water. Dr. Ludwig Neurohr took water samples at various depths, which were then analyzed by the whole team on land. (For data see gallery Research).

Information and consent to cookies & third-party content

We use technically necessary cookies/tools to offer, operate and secure this service. Furthermore ,with your express consent , we use cookies/tools for marketing, tracking, creating personalised content on third-party sites and for displaying third-party content on our website. You can revoke your consent at any time with effect for the future via the menu item ‘Cookie settings’.
By clicking on ‘Allow all’, you give us your express consent to the use of cookies/tools to improve the quality and performance of our service, for functional and personalised performance optimisation, to measure the effectiveness of our ads or campaigns, for personalised content for marketing purposes, including outside our website. This enables us to provide personalised online ads and extended analysis options about your user behaviour. This also includes accessing and storing data on your device. You can revoke your consent at any time with effect for the future via the menu item ‘Cookie settings’.
You can use the ‘Change settings’ button to grant and revoke individual consent to the cookies/tools and receive further information on the cookies/tools we use, their purposes and duration.
By clicking on ‘Only absolutely necessary’, only technically necessary cookies/tools are used.

Our data protection declaration tells you how we process personal data and what purposes we use the data processing for.

PUSH messages from JBL

What are PUSH messages? As part of the W3C standard, web notifications define an API for end-user notifications that are sent to the user's desktop and/or mobile devices via the browser. Notifications appear on the end devices as they are familiar to the end user from apps installed on the device (e.g. emails). Notifications appear on the end user’s device, just like an app (e.g. for emails) installed on the device.

These notifications enable a website operator to contact its users whenever they have a browser open - it doesn’t matter whether the user is currently visiting the website or not.

To be able to send web push notifications, all you need is a website with a web push code installed. This allows brands without apps to take advantage of many of the benefits of push notifications (personalised real-time communications at just the right moment).

Web notifications are part of the W3C standard and define an API for end user notifications. A notification makes it possible to inform the user about an event, such as a new blog post, outside the context of a website.

JBL GmbH & Co. KG provides this service free of charge, and it is easy to activate or deactivate.