Would you take a 6 week old to Disney???

ok, I priced out a couple of vacations just to see how much of a deal you would be getting or not getting. If you go 9/23-9/30 , to Pop Century, with free dining, and 7-day base tickets for 2a, 1c the total would be $1226.06. If you went 12/2 - 12/9, to Pop Century, pay for dining plan, 7-day base tickets, it's $1847.39. HOWEVER...for about $55, you can join AAA which would save about $25/night on the December trip...making that total 1847+55-175=1727 for the package.

If you buy the components separately for a December trip: Ticketmania 2a 1c 7-day base tickets: $584 (shipping added in already. Would be a little less, with mousesavers newsletter discount). Pop Century 12/2-12/9 through AAA: $493.28 (after tax). Grand total: $1077.28 but you would buy your own food. The good thing about that, though, is that you only buy what you will actually eat.


HTH with your decision-making process!!
Only you can decide what the savings means to your family. Whatever you decide, enjoy your new baby and your trip, if you take it!
 
I wouldn't plan a non-refundable trip for then. My last child had "issues" at birth, and at 6 weeks old we were just coming out of the woods. There's so much you just can't know until the baby is here, healthwise, temperament wise, sleepwise, etc.

We took her to WDW at 5 months old, and by then she was fine and enjoyed it as much as a 5mo can. (The trip was for her older siblings, and she went along for the ride!)
 
you also need to check with your health insurance carrier-some have realy wierd provisions regarding medical care out of state (my hmo covers nothing unless it's "life threatening", and my former ppo uped the patient co-pay from 10% to 50% on a pregnant woman in the last so many weeks of the pregnancy/an infant under so many weeks of age if they required medical treatment while traveling more than 50 miles from their home). i don't think you can buy travelers health insurance on an unborn, and they usualy don't sell decent cancelation insurance less than 90 days out from the date of travel so it might be unlikly that you could even get cancelation insurance that would cover an issue of cancelation due to a new or recent born baby issue.
 
Personally I wouldn't do it for many of the reasons already mentioned.
 

I took my son to a Tuscon riding resort/spa when he was 7 weeks AND the Grand Canyon. He was a suprise adoption so we had planned the trip not knowing we'd have him. Having done that, I doubt I would take a baby that young to WDW. They can be pretty fragile and the heat at the end of September can be intense. My son did well on our trip but we had a rented air conditioned villa and someone was always with him there-we were not in theme parks. When we went to the Grand Canyon, he rode in a snuggly and it was much cooler than in Tuscon. THAT two days of somewhat heavy activity did him in. He really got screaming at the end of them. I felt horrible and knew we needed to be more baby oriented from then on. I'm voting no but I won't judge you if you do it.
 
I took my DD to WDW when she was 3 months old. Everything went great! My sister brought her son when he was about 6 weeks old. I thought he was a bit too young for the heat, crowds, etc. I understand the call of free dining, but what about a trip in early December instead?
 
TheDisneyBunch said:
Ok need some opinions. I asked something like this a while back. We have been trying our best to figure out how we can work in a Disney trip this year with the baby being due the first of Sept. Well.. my dr will induce at 38 weeks if I want her to which I know I will. I had my son at 38 weeks and he was over 8lbs and I was so ready for him at that point..lol So anyways, that would put me having him August 20th. We want to schedual a Disney trip for Sept 30th for 6 nights with free dining at POR. We would be taking our almost 4 year old and then the new baby which would be 6 weeks by then. Is this a terrible idea? Anyone ever tried going with a baby before? I am not worried about missing rides or anything. I love going for the atmosphere, the fun my son has, pin trading, good meals, enjoying the resort, etc... I am just kind of torn. I really want us to be able to go and it has been driving us crazy thinking of not getting to plan a trip this year and this is the best solution we can come up with is to go on the very last possible day of free dining and take the baby. I just don't want that to be too much for the baby or anything, ya know? Opinions??

No need for anyone to be rude though.. ;) Had some rude comments to my last question like this. :rolleyes:

Thanks for any thoughts guys! We are having the hardest time making up our minds but really WANT to go. :love:

GO!!!!!

The beginning of October is a great time as the temps won't be pounding hot in the afternoons. It will be warm but not stifling hot! There are so many rides you can take baby on with you too! Also in Sept and the beginning of October, all the schools in the US are back in session and the crowds will be lighter. (The last 3 weeks brings in the visitors from England as they go "on holiday" and all come to Florida!)

Tomorrowland Transit Authority will be a nice break during the day from walking!
Buzz Lightyear will be mild enough for you to hold a 6 week old
Jungle Cruise
Pirates of the Cribbean
Tiki Room
WDW Railroad is always fun
Small World of course
Mickeys Philharmagic
Winnie the Pooh
Are just some of the things that you will all be able to do together.
Just go and have a relaxing time and don't worry about the baby or what other people might think about taking a baby to WDW. :sunny:
 
I wouldn't do it. I had a really rough delivery, sever PPD and a colicky, so at 6 weeks I could hardly make it out of bed, let alone walk around WDW.

We did go for 2 nights when DS was about 12 weeks old and that was ok but the heat did get to him.

In your situation with a new baby and your DH being laid off, I'd have to save the extra $.
 
I just read that December wasn't a good time because your DH will be laid off and then will be attending school in January. If you can afford to do POR with free dining in September then you can afford to book a Value resort in December and add the dining. The differece is less than $100. You can budget now for the trip and set money aside in advance. Then, go to WDW when you DH is laid off. Perhaps he can take his vacation at the end of the year so you can go early enough to avoid the holiday time. If you're worried about spending money after he is laid off, then you shouldn't go in September either.
 
I think you KNOW what you Should DO but what you WANT to do is pulling another direction and you hoped we would validate it for you. (I hope that doesn't sound rude). I am way too practical to 1) take an optional trip with a child that young and 2) too cheap to do it knowing that DH would be laid off a few months later.

You have a very young family and WDW is not going anywhere. I would wait until things were more stable all the way around. You won't be able to enjoy WDW with your older child if you have to tend to the baby and that won't be much of a trip for him.

JMO - and that is what you asked for.
 
Here is my 2 cents..now, i do not begrudge anyone wanting to go to Disney ANYTIME, so please, listen to my opinion, and use to help make up your mind, but please don't think I am telling you this because I do not want you to go. Ultimately, it is your decision.

My friend had a Disney trip planned for over a year, to take her granddaughter down. GD was 4yo. Her daughter got pregnant in that year, and the baby was born in April, with the trip scheduled for June. They went back and forth, trying to decide to cancel the trip or not, because of the baby, but decided to bring the baby. They had a good time, but the trip was very stressful, because it was so hot, they worried about keeping the baby out of the hot sun and heat.

To quote my friend "It was awful." They just worried so much about the baby, it did effect their vacation somewhat. If she were responding to this OP, I am sure she would tell you to wait a few months, but since I can only go by hearing about her experience, I pass it on to you, and you can consider it. It is still pretty hot down there in September, so you need to consider if trying to keep the baby cool will limit what you can do with the 4yo.

I will tell you, we went down when my youngest was only 8 months old, and let me just say, he had a BLAST. I never would of imagined an 8 month old would know enough to know he was somewhere special, but that kid woke up every day, and as soon as we started the sunblock patrol on all the kids, he would be SQUEALING with delight.
 
I'd definetly wait. Disney will always be there.
The health and welfare of a newborn is more important.
The sun is too strong for a baby that age, when you will be outside alot.

I know it hurts not to go, but you're probably better off waiting a bit.
Good luck in your decision :)
 
figment52 said:
I think you KNOW what you Should DO but what you WANT to do is pulling another direction and you hoped we would validate it for you. (I hope that doesn't sound rude). I am way too practical to 1) take an optional trip with a child that young and 2) too cheap to do it knowing that DH would be paid off a few months later.

You have a very young family and WDW is not going anywhere. I would wait until things were more stable all the way around. You won't be able to enjoy WDW with your older child if you have to tend to the baby and that won't be much of a trip for him.

JMO - and that is what you asked for.

You said exactly what I was thinking. I too am too practical and cheap. I could never even consider it. But that's me.
 
While you may have bounced back after your first, remember, you have another child and you won't be able to nap when the baby naps which will make a difference in how you feel 6 weeks postpartum.

Personally, I wouldn't take a newborn to Disney. There are just too many things that could go wrong. We saw a newborn one day and it was HOT. The poor baby was beet red, hot, not sunburn. I couldn't believe it. Sorry, I just don't think it is a good idea all the way around.
 
I wouldn't do it. Way too many what if's , right down to hurricane weather! I'd wait a few months. I also thought my second baby would be really big and she was 2 lbs smaller than her brother, you can't count on babies being bigger each time! Good luck!
 
Thanks for all the opinions guys. This is just something we thought about and were toying with so I wanted to get opinions.

We would definately get trip insurance so that if anything came up we could cancel.

For those concerned over me being induced "early" (38 weeks is term), I would be doing this anyways as long as the baby is ready. I am not saying i would induce just to go on a trip. My dr will induce at 38 weeks for anyone who had a previous big baby early and who they have determined has a baby who is ready. Yes I realize this could change last minute and that is why we would have the insurance. :)

If he were born at 40 weeks then no I would not want to go at all. 6 weeks is when they are old enough to start daycare (not that I do daycare) just saying that the dr feels they are old enough by then to be in daycare. So at 4 weeks I would not want to take him. I also do not think I would be up for it at 4 weeks at all. So yes those 2 weeks would definately make the choice of going or not going much easier..lol

I would LOVE LOVE LOVE to go in December. Trust me I have been working on dh about that one a lot..lol I figured that whole thing out too about staying in a value resort and buying the dining and it costing about the same as going in Sept and staying at POR. I was thinking it sounded great...I tell dh and he is not happy about it b/c he is not saving any money. Thanks to the poster who said something about AAA. I will have to check into that. Hubby is just one of those people who HAS to be getting a great deal or does not want to do it. and he wants to go worse than me I think..lol For me, I would much rather go in December!!

As I said before I am worried about the heat and such. This was why I asked for opinions. I knew there were things that I was not thinking about fully. I was just thinking for example, that this delivery and recovery would be as easy as it was the first time..which was certainly not easy but I was ok by 6 weeks pp. Then I also was only thinking about what a good baby my son was and how easy he was and that he would have done fine at 6 weeks anywhere I took him. I have not thought much about this baby being a much harder baby.

Sleeping through the night is not an issue for us. We have crazy sleep hours anyways b/c hubby works 2nd shift. We have never had trouble with different sleeping hours. My son sleeps in our room for the most part and the new baby will too so sharing a room while we sleep is also not a issue for us b/c we would be doing it at home. ;)

We would not be flying. We would be driving. I would not want to take the baby to the airport and put them on a plane at that age yet.

So the things I worry most about are the heat and the germs. I would be scared of feeling like I needed to get the baby back to the room all the time to keep him cool. With the germs I just felt Disney is so open he would not be that exposed to it..not like we will be trapped in a small room with people breathing all over him or I would leave..lol I am one of the most overprotective mommas in the world. This is why I stay home with my son..don't like daycares, don't trust others with him, etc. I don't let him be around lots of other kids b.c I don't want him catching things from them, etc.. I still do everything for him..baby him TOO much..lol I know I will be the same with the new baby and be really overprotective. SO I am sure once the baby got here my feelings would be different than they are now. It is so hard for me to remember that small stage since my son is over 3 now. ;) I keep telling myself it will be easy and all.

All in all I realize the trip is not the best idea and it is b/c you guys brought up things I was not thinking about. This is why I asked for opinions to help me decide b/c I knew I was not taking all things into consideration. I appreciate all the thoughts on it.

Sorry to ramble, just wanted to clear up a few things that people had brought up. :)
 
No, I wouldn't take a 6 week old. And I probably wouldn't plan a trip with an impending layoff either, IMO. :)
 
When I was a cast member I once saw a baby that was only 2 weeks old. It was Mother's Day, and the parents were excited to show the new baby off. They were all very happy, and the baby seemed very content. But I believe they were Florida residents, and didn't have to travel far.

As long as you and your baby are comfortable, I see no problem with it.
 

New Posts


Disney Vacation Planning. Free. Done for You.
Our Authorized Disney Vacation Planners are here to provide personalized, expert advice, answer every question, and uncover the best discounts. Let Dreams Unlimited Travel take care of all the details, so you can sit back, relax, and enjoy a stress-free vacation.
Start Your Disney Vacation
Disney EarMarked Producer






DIS Facebook DIS youtube DIS Instagram DIS Pinterest DIS Tiktok DIS Twitter
Add as a preferred source on Google

Back
Top Bottom