ArtsAutosBooksBusinessEducationEntertainmentFamilyFashionFoodGamesGenderHealthHolidaysHomeHubPagesPersonal FinancePetsPoliticsReligionSportsTechnologyTravel

The Breach of the Greek Front Line at Afyon 1922

Updated on July 1, 2010
Breakthru of the Turk cavalry Aug 27 at Duplumpinar, a key railway station. Greek units east of this were unsupplied.
Breakthru of the Turk cavalry Aug 27 at Duplumpinar, a key railway station. Greek units east of this were unsupplied.

 

The 14th August brought the final blow and the Greek front line was breached. Kemal’s plan was to strike between the river Tsai and Bonnar, the most vulnerable point in the front line. The Greek side put all forces of the 7th Division into action at the breach so the plan to counter-attack was cancelled. The 7th Division commanding officer took over from the 5th Infantry who had fled.  The 1st and 7th divisions were barely holding the line.

 

Losses increased. The Turkish cavalry pounded the 1st Division from the south. Frangou ordered a strong counter-attack as instructed, but the 2nd Division was tackling Turkish cavalry north of the railway line. The counter-attack at Savran never got underway and at Hasan Bel it was feeble. Only two regiments of reinforcements arrived during the night. While the Turks threw all their reserves into the battle and their cavalry still kept coming through Tsai Hisar pass, the Greek 2nd & 3rd Corps waited for orders from Izmir. The attack at the east of Kiri Bel sent 2 battalions from the 22nd and 1 from the 49th into retreat. The western section held out until 09.00. Some 24 Turk bns attack the 5/4( single battalion!). The enemy had already reached Sinirkii Gorge and the 37th’s counter-attack collapsed under Turkish artillery fire. At 11.30 Kitriniari railway station fell, this cut off many Greek units and their supply line. Tilki Bel finally fell at 13.00 and the disorderly retreat spread to the 4th & 49th Infantry at Kayiandibi and Kilitz Arslan. Sections of 23rd followed suit. The whole left flank of 1st Division had been breached by 13.00 and,  in spite of Frangou’s efforts, the retreat was unstoppable (which would become a greek rout). In one section, some 500-700 men attack across barb wire defended by 150 men. Only 50 men survive.

 

 At Hasan Bel the 5th Infantry fought on but further east the 4th Division had retreated. At 06.00 Prionidis hill fell and the 35th Infantry withdrew 600 metres, leaving two openings for the Turks to reach Afyon. At 07.00 Karasi fell and P1/35 retreated. The Turks advanced towards Moutatibi Dag and the breach widened. Plastiras’ detachment at Katsibali station and hill 1.310 were now pounded from both sides. Kemelar at the 4th Division’s right flank was in flames. At 08.00 hill 1.310 fell and double company Kokkino and 3/42 company were forced to retreat. Plastiras stepped in and gave an impossible order that the hill be retaken. Tertika Battalion attacked with extremely heavy losses. III bn/42 Reg. and I bn/42 were forced to retreat. The 11th Infantry at Kislatzik and the 8th at Seylen suffered tremendous losses. But for action taken by the 26th Infantry, the town of Afyon would have fallen in the morning, with disastrous consequences. While the Greeks were still holding the town of Afyon, many of the arteries of lines of communication and supply were cut. This put the Greek units in the city in a most precarious position, one that would only be a matter of time until either they would become cut-off or be forced to retreat.

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://corp.maven.io/privacy-policy

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)
ClickscoThis is a data management platform studying reader behavior (Privacy Policy)