ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Fight Continues to Continue: Hungary 1944

Updated on March 20, 2009

 October 17 Tuesday

The German High Command had issued its withdrawal order and for the Russians it was clear that Debrecen would soon be theirs. Many of the Russian troops celebrated as they entered into the city fringe, firing their weapons wildly for no reason. The German engineers busily were destroying their manufacturing, stores, railways, etc. Overhead, Russian aircraft buzzed over. German rearguard units contested when they could. Black smoke filled the air towards  Nagyverdo.  This was not a Stalingrad or Breslau situation, the Germans were not determined to hold Debrecen, in fact, they were too weak to do so. The local populace struggled with the lack of food and the Red soldier who committed numerous rapes and other killings upon them.

The Russian Pliyev mechanized and cavalry group was ordered to send the 7th Mechanized Corps from Derecske-Sarand-Mikepercs area into Debrecen. The 4th Guards Cavalry Corps was ordered to attack towards Hajdúszováton and through it to occupy the countryside adjacent to the city. The 6th Guards Cavalry Corps was ordered to advance from Hajdúszoboszló towards Debrecen ending on the northwest side of it.

The 3rd Panzer Corps withdrew in safety as did 1st Panzer Division that also received orders to withdraw at around 0900.

During the day, the German  situation went into critical care, when the Russian Gorskov cavalry and tank group busted through east of Debrecen and advanced towards Mihályfalva. This was a smart Russian to outflank the German defenses surrounding Debrecen. It was a serious issues for between the German 6th and 8th Armies some 40-50 km was NOT defended at all!

 

Such a threat was that some Russian units had reached the 3rd Panzer Corps rear positions sending non-combat troops into a frenzy. Quickly, supply issues arose for the Germans and called upon air supply drops for those units isolated.

 

This emergency actually created a situation where elements of the 24th Panzer Division and the newly arrived 503rd Tiger Tank Battalion were now committed to join the struggling 4th SS PG Division attacking east from Sznolok.

The 24th Panzer left from the DuklaPass on the 11th and arrived in Budapest to quell the potential Hungarian betrayal. The 503rd had also arrived from France for the same purpose. When the 24th Panzer departed from DuklaPass, it had an assortment of tanks in the armor regiment, only 20 Pz IV and StGs. Its 2nd Bn\21st PG and 2nd Bn\26th PG were carried in various types of trucks. Like most of the panzer divisions in Hungary, it was threadbare. Some sources indicate the 24th Panzer Division actually had only three Pz III, 18 StG III, and 22 Pz IV. Its actual strength was a full company. Operationally speaking, on Oct.1, the division could deploy:

 

14 Pz IV

4  StG III

3 Pz III Command

86 APCs

7 Armor Cars with 150mm

The 503rd Tiger Battalion arrived from France. While in France, the unit fought the British near Caen in July. At that time it contained 33 Tiger I and 12 Tiger II. It fought there until September when it was transferred to Paderhorn for refurbishment.  There, it received 45 new Tiger II, and arrived in Hungary to help suppress the Hungarian “coup d’etat” on Oct 13-14.

It arrival at the 4th Panzer Corps near Budapest was welcome but none of the troops had trained together.  It was decided to have the Tiger unit support both the 4th SS PG and 24th Panzer Division in German counterattack.   

The 6th Army was informed that both the 24th Panzer and 503rd Tiger would attack with the 4th SS PG in an effort to relieve the struggling and weakened 3rd Panzer Corps commanded by Breith. The Germans were confident they could bust through a Russian line consisting mostly of infantry. But the Germans were already withdrawing from Debrecen, so any success would be useless. 

As the German counterattack force gather, the real battle continued with the Russian 23rd Tank Corps breaking through towards Mihaly—unobstructed. The only German forces around were weak reconnassiance forces.

 

The downside for the Russians with the numerous breaks in the German lines was that now the Russian units also needed to be resupplied and fueled. This was not easy as the Germans were weak but daring. The Russian spearheads had fragile supply lines, which tenuously stretched farther and farther. While the Russians created havoc for the 3rd Panzer Corps units trying to flee and fight,  by the same token, because of supply, the Russians did not take advantage of the gaps between Kába and Derecske,n Sáránd, or Nagylétát. The Russian success was now starting to hinder them. This allowed some breathing space for the Germans to regroup. Both the German FFH PG and 1st Panzer Divisions needed this.

Terrain and conditions played heavily in favor of the weakened Germans. In the Derecske vicinity was an area that was marshy and small lakes dotted the area. This force the tanks and mechanized troops to stick to roads, which were narrow. Muddy countryside also contributed the Russians inability to exploited across a vast area. All these events forced them to stay close to the main paved roads. The Germans deployed small groups and tanks at all the crossings and in all towns an villages, especially along the main roads. The Russian advance was fast until it was halted at one of the strongpoints and stopped until cleared. German troops were daring and struck back and their skill showed it. The Germans would resist until they were in a dangerous position and then withdraw. This made the advance slow. At one time, the Russian 2nd Cavalry Division and other mechanized forces attempted to out maneuver the Germans at Derecske and wasted much of the day dealing various small German counterattacks. Pliyev ordered his troops to remain close to the roads and concentrate their strength cauisng him major traffic jams.

 

 

Comments

    0 of 8192 characters used
    Post Comment

    No comments yet.

    working

    This website uses cookies

    As a user in the EEA, your approval is needed on a few things. To provide a better website experience, hubpages.com uses cookies (and other similar technologies) and may collect, process, and share personal data. Please choose which areas of our service you consent to our doing so.

    For more information on managing or withdrawing consents and how we handle data, visit our Privacy Policy at: https://hubpages.com/privacy-policy#gdpr

    Show Details
    Necessary
    HubPages Device IDThis is used to identify particular browsers or devices when the access the service, and is used for security reasons.
    LoginThis is necessary to sign in to the HubPages Service.
    Google RecaptchaThis is used to prevent bots and spam. (Privacy Policy)
    AkismetThis is used to detect comment spam. (Privacy Policy)
    HubPages Google AnalyticsThis is used to provide data on traffic to our website, all personally identifyable data is anonymized. (Privacy Policy)
    HubPages Traffic PixelThis is used to collect data on traffic to articles and other pages on our site. Unless you are signed in to a HubPages account, all personally identifiable information is anonymized.
    Amazon Web ServicesThis is a cloud services platform that we used to host our service. (Privacy Policy)
    CloudflareThis is a cloud CDN service that we use to efficiently deliver files required for our service to operate such as javascript, cascading style sheets, images, and videos. (Privacy Policy)
    Google Hosted LibrariesJavascript software libraries such as jQuery are loaded at endpoints on the googleapis.com or gstatic.com domains, for performance and efficiency reasons. (Privacy Policy)
    Features
    Google Custom SearchThis is feature allows you to search the site. (Privacy Policy)
    Google MapsSome articles have Google Maps embedded in them. (Privacy Policy)
    Google ChartsThis is used to display charts and graphs on articles and the author center. (Privacy Policy)
    Google AdSense Host APIThis service allows you to sign up for or associate a Google AdSense account with HubPages, so that you can earn money from ads on your articles. No data is shared unless you engage with this feature. (Privacy Policy)
    Google YouTubeSome articles have YouTube videos embedded in them. (Privacy Policy)
    VimeoSome articles have Vimeo videos embedded in them. (Privacy Policy)
    PaypalThis is used for a registered author who enrolls in the HubPages Earnings program and requests to be paid via PayPal. No data is shared with Paypal unless you engage with this feature. (Privacy Policy)
    Facebook LoginYou can use this to streamline signing up for, or signing in to your Hubpages account. No data is shared with Facebook unless you engage with this feature. (Privacy Policy)
    MavenThis supports the Maven widget and search functionality. (Privacy Policy)
    Marketing
    Google AdSenseThis is an ad network. (Privacy Policy)
    Google DoubleClickGoogle provides ad serving technology and runs an ad network. (Privacy Policy)
    Index ExchangeThis is an ad network. (Privacy Policy)
    SovrnThis is an ad network. (Privacy Policy)
    Facebook AdsThis is an ad network. (Privacy Policy)
    Amazon Unified Ad MarketplaceThis is an ad network. (Privacy Policy)
    AppNexusThis is an ad network. (Privacy Policy)
    OpenxThis is an ad network. (Privacy Policy)
    Rubicon ProjectThis is an ad network. (Privacy Policy)
    TripleLiftThis is an ad network. (Privacy Policy)
    Say MediaWe partner with Say Media to deliver ad campaigns on our sites. (Privacy Policy)
    Remarketing PixelsWe may use remarketing pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to advertise the HubPages Service to people that have visited our sites.
    Conversion Tracking PixelsWe may use conversion tracking pixels from advertising networks such as Google AdWords, Bing Ads, and Facebook in order to identify when an advertisement has successfully resulted in the desired action, such as signing up for the HubPages Service or publishing an article on the HubPages Service.
    Statistics
    Author Google AnalyticsThis is used to provide traffic data and reports to the authors of articles on the HubPages Service. (Privacy Policy)
    ComscoreComScore is a media measurement and analytics company providing marketing data and analytics to enterprises, media and advertising agencies, and publishers. Non-consent will result in ComScore only processing obfuscated personal data. (Privacy Policy)
    Amazon Tracking PixelSome articles display amazon products as part of the Amazon Affiliate program, this pixel provides traffic statistics for those products (Privacy Policy)